Sidelink Bearer Mode Change by a Wireless Device

ABSTRACT

A first wireless device receives, from a base station, configuration parameters for a resource allocation mode 1 of a sidelink bearer between the first wireless device and a second wireless device. The first wireless device receives, from the base station, at least one parameter indicating the sidelink bearer to transition from the resource allocation mode 1 to a resource allocation mode 2. The first wireless device transmits, to the second wireless device, transport blocks via the sidelink bearer based on the resource allocation mode 2.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of International Application No.PCT/US2020/054110, filed Oct. 2, 2020, which claims the benefit of U.S.Provisional Application No. 62/909,412, filed Oct. 2, 2019, all of whichare hereby incorporated by reference in their entireties.

BRIEF DESCRIPTION OF THE DRAWINGS

Examples of several of the various embodiments of the present disclosureare described herein with reference to the drawings.

FIG. 1A and FIG. 1B illustrate example mobile communication networks inwhich embodiments of the present disclosure may be implemented.

FIG. 2A and FIG. 2B respectively illustrate a New Radio (NR) user planeand control plane protocol stack.

FIG. 3 illustrates an example of services provided between protocollayers of the NR user plane protocol stack of FIG. 2A.

FIG. 4A illustrates an example downlink data flow through the NR userplane protocol stack of FIG. 2A.

FIG. 4B illustrates an example format of a MAC subheader in a MAC PDU.

FIG. 5A and FIG. 5B respectively illustrate a mapping between logicalchannels, transport channels, and physical channels for the downlink anduplink.

FIG. 6 is an example diagram showing RRC state transitions of a UE.

FIG. 7 illustrates an example configuration of an NR frame into whichOFDM symbols are grouped.

FIG. 8 illustrates an example configuration of a slot in the time andfrequency domain for an NR carrier.

FIG. 9 illustrates an example of bandwidth adaptation using threeconfigured BWPs for an NR carrier.

FIG. 10A illustrates three carrier aggregation configurations with twocomponent carriers.

FIG. 10B illustrates an example of how aggregated cells may beconfigured into one or more PUCCH groups.

FIG. 11A illustrates an example of an SS/PBCH block structure andlocation.

FIG. 11B illustrates an example of CSI-RSs that are mapped in the timeand frequency domains.

FIG. 12A and FIG. 12B respectively illustrate examples of three downlinkand uplink beam management procedures.

FIG. 13A, FIG. 13B, and FIG. 13C respectively illustrate a four-stepcontention-based random access procedure, a two-step contention-freerandom access procedure, and another two-step random access procedure.

FIG. 14A illustrates an example of CORESET configurations for abandwidth part.

FIG. 14B illustrates an example of a CCE-to-REG mapping for DCItransmission on a CORESET and PDCCH processing.

FIG. 15 illustrates an example of a wireless device in communicationwith a base station.

FIG. 16A, FIG. 16B, FIG. 16C, and FIG. 16D illustrate example structuresfor uplink and downlink transmission.

FIG. 17A, FIG. 17B, FIG. 17C, and FIG. 17D is an example diagram of anaspect of an embodiment of the present disclosure.

FIGS. 18A and 18B is an example diagram of an aspect of an embodiment ofthe present disclosure.

FIG. 19 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 20 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 21 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 22 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 23 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 24 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 25 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 26 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 27 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 28 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 29 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 30 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 31 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 32 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 33 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 34 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 35 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 36 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 37 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 38 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

DETAILED DESCRIPTION

In the present disclosure, various embodiments are presented as examplesof how the disclosed techniques may be implemented and/or how thedisclosed techniques may be practiced in environments and scenarios. Itwill be apparent to persons skilled in the relevant art that variouschanges in form and detail can be made therein without departing fromthe scope. In fact, after reading the description, it will be apparentto one skilled in the relevant art how to implement alternativeembodiments. The present embodiments should not be limited by any of thedescribed exemplary embodiments. The embodiments of the presentdisclosure will be described with reference to the accompanyingdrawings. Limitations, features, and/or elements from the disclosedexample embodiments may be combined to create further embodiments withinthe scope of the disclosure. Any figures which highlight thefunctionality and advantages, are presented for example purposes only.The disclosed architecture is sufficiently flexible and configurable,such that it may be utilized in ways other than that shown. For example,the actions listed in any flowchart may be re-ordered or only optionallyused in some embodiments.

Embodiments may be configured to operate as needed. The disclosedmechanism may be performed when certain criteria are met, for example,in a wireless device, a base station, a radio environment, a network, acombination of the above, and/or the like. Example criteria may bebased, at least in part, on for example, wireless device or network nodeconfigurations, traffic load, initial system set up, packet sizes,traffic characteristics, a combination of the above, and/or the like.When the one or more criteria are met, various example embodiments maybe applied. Therefore, it may be possible to implement exampleembodiments that selectively implement disclosed protocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices and/or base stations may support multiple technologies, and/ormultiple releases of the same technology. Wireless devices may have somespecific capability(ies) depending on wireless device category and/orcapability(ies). When this disclosure refers to a base stationcommunicating with a plurality of wireless devices, this disclosure mayrefer to a subset of the total wireless devices in a coverage area. Thisdisclosure may refer to, for example, a plurality of wireless devices ofa given LTE or 5G release with a given capability and in a given sectorof the base station. The plurality of wireless devices in thisdisclosure may refer to a selected plurality of wireless devices, and/ora subset of total wireless devices in a coverage area which performaccording to disclosed methods, and/or the like. There may be aplurality of base stations or a plurality of wireless devices in acoverage area that may not comply with the disclosed methods, forexample, those wireless devices or base stations may perform based onolder releases of LTE or 5G technology.

In this disclosure, “a” and “an” and similar phrases are to beinterpreted as “at least one” and “one or more.” Similarly, any termthat ends with the suffix “(s)” is to be interpreted as “at least one”and “one or more.” In this disclosure, the term “may” is to beinterpreted as “may, for example.” In other words, the term “may” isindicative that the phrase following the term “may” is an example of oneof a multitude of suitable possibilities that may, or may not, beemployed by one or more of the various embodiments. The terms“comprises” and “consists of”, as used herein, enumerate one or morecomponents of the element being described. The term “comprises” isinterchangeable with “includes” and does not exclude unenumeratedcomponents from being included in the element being described. Bycontrast, “consists of” provides a complete enumeration of the one ormore components of the element being described. The term “based on”, asused herein, should be interpreted as “based at least in part on” ratherthan, for example, “based solely on”. The term “and/or” as used hereinrepresents any possible combination of enumerated elements. For example,“A, B, and/or C” may represent A; B; C; A and B; A and C; B and C; or A,B, and C.

If A and B are sets and every element of A is an element of B, A iscalled a subset of B. In this specification, only non-empty sets andsubsets are considered. For example, possible subsets of B={cell1,cell2} are: {cell1}, {cell2}, and {cell1, cell2}. The phrase “based on”(or equally “based at least on”) is indicative that the phrase followingthe term “based on” is an example of one of a multitude of suitablepossibilities that may, or may not, be employed to one or more of thevarious embodiments. The phrase “in response to” (or equally “inresponse at least to”) is indicative that the phrase following thephrase “in response to” is an example of one of a multitude of suitablepossibilities that may, or may not, be employed to one or more of thevarious embodiments. The phrase “depending on” (or equally “depending atleast to”) is indicative that the phrase following the phrase “dependingon” is an example of one of a multitude of suitable possibilities thatmay, or may not, be employed to one or more of the various embodiments.The phrase “employing/using” (or equally “employing/using at least”) isindicative that the phrase following the phrase “employing/using” is anexample of one of a multitude of suitable possibilities that may, or maynot, be employed to one or more of the various embodiments.

The term configured may relate to the capacity of a device whether thedevice is in an operational or non-operational state. Configured mayrefer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ornon-operational state. In other words, the hardware, software, firmware,registers, memory values, and/or the like may be “configured” within adevice, whether the device is in an operational or nonoperational state,to provide the device with specific characteristics. Terms such as “acontrol message to cause in a device” may mean that a control messagehas parameters that may be used to configure specific characteristics ormay be used to implement certain actions in the device, whether thedevice is in an operational or non-operational state.

In this disclosure, parameters (or equally called, fields, orInformation elements: IEs) may comprise one or more information objects,and an information object may comprise one or more other objects. Forexample, if parameter (IE) N comprises parameter (IE) M, and parameter(IE) M comprises parameter (IE) K, and parameter (IE) K comprisesparameter (information element) J. Then, for example, N comprises K, andN comprises J. In an example embodiment, when one or more messagescomprise a plurality of parameters, it implies that a parameter in theplurality of parameters is in at least one of the one or more messages,but does not have to be in each of the one or more messages.

Many features presented are described as being optional through the useof “may” or the use of parentheses. For the sake of brevity andlegibility, the present disclosure does not explicitly recite each andevery permutation that may be obtained by choosing from the set ofoptional features. The present disclosure is to be interpreted asexplicitly disclosing all such permutations. For example, a systemdescribed as having three optional features may be embodied in sevenways, namely with just one of the three possible features, with any twoof the three possible features or with three of the three possiblefeatures.

Many of the elements described in the disclosed embodiments may beimplemented as modules. A module is defined here as an element thatperforms a defined function and has a defined interface to otherelements. The modules described in this disclosure may be implemented inhardware, software in combination with hardware, firmware, wetware (e.g.hardware with a biological element) or a combination thereof, which maybe behaviorally equivalent. For example, modules may be implemented as asoftware routine written in a computer language configured to beexecuted by a hardware machine (such as C, C++, Fortran, Java, Basic,Matlab or the like) or a modeling/simulation program such as Simulink,Stateflow, GNU Octave, or Lab VIEWMathScript. It may be possible toimplement modules using physical hardware that incorporates discrete orprogrammable analog, digital and/or quantum hardware. Examples ofprogrammable hardware comprise: computers, microcontrollers,microprocessors, application-specific integrated circuits (ASICs); fieldprogrammable gate arrays (FPGAs); and complex programmable logic devices(CPLDs). Computers, microcontrollers and microprocessors are programmedusing languages such as assembly, C, C++ or the like. FPGAs, ASICs andCPLDs are often programmed using hardware description languages (HDL)such as VHSIC hardware description language (VHDL) or Verilog thatconfigure connections between internal hardware modules with lesserfunctionality on a programmable device. The mentioned technologies areoften used in combination to achieve the result of a functional module.

FIG. 1A illustrates an example of a mobile communication network 100 inwhich embodiments of the present disclosure may be implemented. Themobile communication network 100 may be, for example, a public landmobile network (PLMN) run by a network operator. As illustrated in FIG.1A, the mobile communication network 100 includes a core network (CN)102, a radio access network (RAN) 104, and a wireless device 106.

The CN 102 may provide the wireless device 106 with an interface to oneor more data networks (DNs), such as public DNs (e.g., the Internet),private DNs, and/or intra-operator DNs. As part of the interfacefunctionality, the CN 102 may set up end-to-end connections between thewireless device 106 and the one or more DNs, authenticate the wirelessdevice 106, and provide charging functionality.

The RAN 104 may connect the CN 102 to the wireless device 106 throughradio communications over an air interface. As part of the radiocommunications, the RAN 104 may provide scheduling, radio resourcemanagement, and retransmission protocols. The communication directionfrom the RAN 104 to the wireless device 106 over the air interface isknown as the downlink and the communication direction from the wirelessdevice 106 to the RAN 104 over the air interface is known as the uplink.Downlink transmissions may be separated from uplink transmissions usingfrequency division duplexing (FDD), time-division duplexing (TDD),and/or some combination of the two duplexing techniques.

The term wireless device may be used throughout this disclosure to referto and encompass any mobile device or fixed (non-mobile) device forwhich wireless communication is needed or usable. For example, awireless device may be a telephone, smart phone, tablet, computer,laptop, sensor, meter, wearable device, Internet of Things (IoT) device,vehicle road side unit (RSU), relay node, automobile, and/or anycombination thereof. The term wireless device encompasses otherterminology, including user equipment (UE), user terminal (UT), accessterminal (AT), mobile station, handset, wireless transmit and receiveunit (WTRU), and/or wireless communication device.

The RAN 104 may include one or more base stations (not shown). The termbase station may be used throughout this disclosure to refer to andencompass a Node B (associated with UMTS and/or 3G standards), anEvolved Node B (eNB, associated with E-UTRA and/or 4G standards), aremote radio head (RRH), a baseband processing unit coupled to one ormore RRHs, a repeater node or relay node used to extend the coveragearea of a donor node, a Next Generation Evolved Node B (ng-eNB), aGeneration Node B (gNB, associated with NR and/or 5G standards), anaccess point (AP, associated with, for example, WiFi or any othersuitable wireless communication standard), and/or any combinationthereof. A base station may comprise at least one gNB Central Unit(gNB-CU) and at least one a gNB Distributed Unit (gNB-DU).

A base station included in the RAN 104 may include one or more sets ofantennas for communicating with the wireless device 106 over the airinterface. For example, one or more of the base stations may includethree sets of antennas to respectively control three cells (or sectors).The size of a cell may be determined by a range at which a receiver(e.g., a base station receiver) can successfully receive thetransmissions from a transmitter (e.g., a wireless device transmitter)operating in the cell. Together, the cells of the base stations mayprovide radio coverage to the wireless device 106 over a wide geographicarea to support wireless device mobility.

In addition to three-sector sites, other implementations of basestations are possible. For example, one or more of the base stations inthe RAN 104 may be implemented as a sectored site with more or less thanthree sectors. One or more of the base stations in the RAN 104 may beimplemented as an access point, as a baseband processing unit coupled toseveral remote radio heads (RRHs), and/or as a repeater or relay nodeused to extend the coverage area of a donor node. A baseband processingunit coupled to RRHs may be part of a centralized or cloud RANarchitecture, where the baseband processing unit may be eithercentralized in a pool of baseband processing units or virtualized. Arepeater node may amplify and rebroadcast a radio signal received from adonor node. A relay node may perform the same/similar functions as arepeater node but may decode the radio signal received from the donornode to remove noise before amplifying and rebroadcasting the radiosignal.

The RAN 104 may be deployed as a homogenous network of macrocell basestations that have similar antenna patterns and similar high-leveltransmit powers. The RAN 104 may be deployed as a heterogeneous network.In heterogeneous networks, small cell base stations may be used toprovide small coverage areas, for example, coverage areas that overlapwith the comparatively larger coverage areas provided by macrocell basestations. The small coverage areas may be provided in areas with highdata traffic (or so-called “hotspots”) or in areas with weak macrocellcoverage. Examples of small cell base stations include, in order ofdecreasing coverage area, microcell base stations, picocell basestations, and femtocell base stations or home base stations.

The Third-Generation Partnership Project (3GPP) was formed in 1998 toprovide global standardization of specifications for mobilecommunication networks similar to the mobile communication network 100in FIG. 1A. To date, 3GPP has produced specifications for threegenerations of mobile networks: a third generation (3G) network known asUniversal Mobile Telecommunications System (UMTS), a fourth generation(4G) network known as Long-Term Evolution (LTE), and a fifth generation(5G) network known as 5G System (5GS). Embodiments of the presentdisclosure are described with reference to the RAN of a 3GPP 5G network,referred to as next-generation RAN (NG-RAN). Embodiments may beapplicable to RANs of other mobile communication networks, such as theRAN 104 in FIG. 1A, the RANs of earlier 3G and 4G networks, and those offuture networks yet to be specified (e.g., a 3GPP 6G network). NG-RANimplements 5G radio access technology known as New Radio (NR) and may beprovisioned to implement 4G radio access technology or other radioaccess technologies, including non-3GPP radio access technologies.

FIG. 1B illustrates another example mobile communication network 150 inwhich embodiments of the present disclosure may be implemented. Mobilecommunication network 150 may be, for example, a PLMN run by a networkoperator. As illustrated in FIG. 1B, mobile communication network 150includes a 5G core network (5G-CN) 152, an NG-RAN 154, and UEs 156A and156B (collectively UEs 156). These components may be implemented andoperate in the same or similar manner as corresponding componentsdescribed with respect to FIG. 1A.

The 5G-CN 152 provides the UEs 156 with an interface to one or more DNs,such as public DNs (e.g., the Internet), private DNs, and/orintra-operator DNs. As part of the interface functionality, the 5G-CN152 may set up end-to-end connections between the UEs 156 and the one ormore DNs, authenticate the UEs 156, and provide charging functionality.Compared to the CN of a 3GPP 4G network, the basis of the 5G-CN 152 maybe a service-based architecture. This means that the architecture of thenodes making up the 5G-CN 152 may be defined as network functions thatoffer services via interfaces to other network functions. The networkfunctions of the 5G-CN 152 may be implemented in several ways, includingas network elements on dedicated or shared hardware, as softwareinstances running on dedicated or shared hardware, or as virtualizedfunctions instantiated on a platform (e.g., a cloud-based platform).

As illustrated in FIG. 1B, the 5G-CN 152 includes an Access and MobilityManagement Function (AMF) 158A and a User Plane Function (UPF) 158B,which are shown as one component AMF/UPF 158 in FIG. 1B for ease ofillustration. The UPF 158B may serve as a gateway between the NG-RAN 154and the one or more DNs. The UPF 158B may perform functions such aspacket routing and forwarding, packet inspection and user plane policyrule enforcement, traffic usage reporting, uplink classification tosupport routing of traffic flows to the one or more DNs, quality ofservice (QoS) handling for the user plane (e.g., packet filtering,gating, uplink/downlink rate enforcement, and uplink trafficverification), downlink packet buffering, and downlink data notificationtriggering. The UPF 158B may serve as an anchor point forintra-/inter-Radio Access Technology (RAT) mobility, an externalprotocol (or packet) data unit (PDU) session point of interconnect tothe one or more DNs, and/or a branching point to support a multi-homedPDU session. The UEs 156 may be configured to receive services through aPDU session, which is a logical connection between a UE and a DN.

The AMF 158A may perform functions such as Non-Access Stratum (NAS)signaling termination, NAS signaling security, Access Stratum (AS)security control, inter-CN node signaling for mobility between 3GPPaccess networks, idle mode UE reachability (e.g., control and executionof paging retransmission), registration area management, intra-systemand inter-system mobility support, access authentication, accessauthorization including checking of roaming rights, mobility managementcontrol (subscription and policies), network slicing support, and/orsession management function (SMF) selection. NAS may refer to thefunctionality operating between a CN and a UE, and AS may refer to thefunctionality operating between the UE and a RAN.

The 5G-CN 152 may include one or more additional network functions thatare not shown in FIG. 1B for the sake of clarity. For example, the 5G-CN152 may include one or more of a Session Management Function (SMF), anNR Repository Function (NRF), a Policy Control Function (PCF), a NetworkExposure Function (NEF), a Unified Data Management (UDM), an ApplicationFunction (AF), and/or an Authentication Server Function (AUSF).

The NG-RAN 154 may connect the 5G-CN 152 to the UEs 156 through radiocommunications over the air interface. The NG-RAN 154 may include one ormore gNBs, illustrated as gNB 160A and gNB 160B (collectively gNBs 160)and/or one or more ng-eNBs, illustrated as ng-eNB 162A and ng-eNB 162B(collectively ng-eNBs 162). The gNBs 160 and ng-eNBs 162 may be moregenerically referred to as base stations. The gNBs 160 and ng-eNBs 162may include one or more sets of antennas for communicating with the UEs156 over an air interface. For example, one or more of the gNBs 160and/or one or more of the ng-eNBs 162 may include three sets of antennasto respectively control three cells (or sectors). Together, the cells ofthe gNBs 160 and the ng-eNBs 162 may provide radio coverage to the UEs156 over a wide geographic area to support UE mobility.

As shown in FIG. 1B, the gNBs 160 and/or the ng-eNBs 162 may beconnected to the 5G-CN 152 by means of an NG interface and to other basestations by an Xn interface. The NG and Xn interfaces may be establishedusing direct physical connections and/or indirect connections over anunderlying transport network, such as an internet protocol (IP)transport network. The gNBs 160 and/or the ng-eNBs 162 may be connectedto the UEs 156 by means of a Uu interface. For example, as illustratedin FIG. 1B, gNB 160A may be connected to the UE 156A by means of a Uuinterface. The NG, Xn, and Uu interfaces are associated with a protocolstack. The protocol stacks associated with the interfaces may be used bythe network elements in FIG. 1B to exchange data and signaling messagesand may include two planes: a user plane and a control plane. The userplane may handle data of interest to a user. The control plane mayhandle signaling messages of interest to the network elements.

The gNBs 160 and/or the ng-eNBs 162 may be connected to one or moreAMF/UPF functions of the 5G-CN 152, such as the AMF/UPF 158, by means ofone or more NG interfaces. For example, the gNB 160A may be connected tothe UPF 158B of the AMF/UPF 158 by means of an NG-User plane (NG-U)interface. The NG-U interface may provide delivery (e.g., non-guaranteeddelivery) of user plane PDUs between the gNB 160A and the UPF 158B. ThegNB 160A may be connected to the AMF 158A by means of an NG-Controlplane (NG-C) interface. The NG-C interface may provide, for example, NGinterface management, UE context management, UE mobility management,transport of NAS messages, paging, PDU session management, andconfiguration transfer and/or warning message transmission.

The gNBs 160 may provide NR user plane and control plane protocolterminations towards the UEs 156 over the Uu interface. For example, thegNB 160A may provide NR user plane and control plane protocolterminations toward the UE 156A over a Uu interface associated with afirst protocol stack. The ng-eNBs 162 may provide Evolved UMTSTerrestrial Radio Access (E-UTRA) user plane and control plane protocolterminations towards the UEs 156 over a Uu interface, where E-UTRArefers to the 3GPP 4G radio-access technology. For example, the ng-eNB162B may provide E-UTRA user plane and control plane protocolterminations towards the UE 156B over a Uu interface associated with asecond protocol stack.

The 5G-CN 152 was described as being configured to handle NR and 4Gradio accesses. It will be appreciated by one of ordinary skill in theart that it may be possible for NR to connect to a 4G core network in amode known as “non-standalone operation.” In non-standalone operation, a4G core network is used to provide (or at least support) control-planefunctionality (e.g., initial access, mobility, and paging). Althoughonly one AMF/UPF 158 is shown in FIG. 1B, one gNB or ng-eNB may beconnected to multiple AMF/UPF nodes to provide redundancy and/or to loadshare across the multiple AMF/UPF nodes.

As discussed, an interface (e.g., Uu, Xn, and NG interfaces) between thenetwork elements in FIG. 1B may be associated with a protocol stack thatthe network elements use to exchange data and signaling messages. Aprotocol stack may include two planes: a user plane and a control plane.The user plane may handle data of interest to a user, and the controlplane may handle signaling messages of interest to the network elements.

FIG. 2A and FIG. 2B respectively illustrate examples of NR user planeand NR control plane protocol stacks for the Uu interface that liesbetween a UE 210 and a gNB 220. The protocol stacks illustrated in FIG.2A and FIG. 2B may be the same or similar to those used for the Uuinterface between, for example, the UE 156A and the gNB 160A shown inFIG. 1B.

FIG. 2A illustrates a NR user plane protocol stack comprising fivelayers implemented in the UE 210 and the gNB 220. At the bottom of theprotocol stack, physical layers (PHYs) 211 and 221 may provide transportservices to the higher layers of the protocol stack and may correspondto layer 1 of the Open Systems Interconnection (OSI) model. The nextfour protocols above PHYs 211 and 221 comprise media access controllayers (MACs) 212 and 222, radio link control layers (RLCs) 213 and 223,packet data convergence protocol layers (PDCPs) 214 and 224, and servicedata application protocol layers (SDAPs) 215 and 225. Together, thesefour protocols may make up layer 2, or the data link layer, of the OSImodel.

FIG. 3 illustrates an example of services provided between protocollayers of the NR user plane protocol stack. Starting from the top ofFIG. 2A and FIG. 3, the SDAPs 215 and 225 may perform QoS flow handling.The UE 210 may receive services through a PDU session, which may be alogical connection between the UE 210 and a DN. The PDU session may haveone or more QoS flows. A UPF of a CN (e.g., the UPF 158B) may map IPpackets to the one or more QoS flows of the PDU session based on QoSrequirements (e.g., in terms of delay, data rate, and/or error rate).The SDAPs 215 and 225 may perform mapping/de-mapping between the one ormore QoS flows and one or more data radio bearers. Themapping/de-mapping between the QoS flows and the data radio bearers maybe determined by the SDAP 225 at the gNB 220. The SDAP 215 at the UE 210may be informed of the mapping between the QoS flows and the data radiobearers through reflective mapping or control signaling received fromthe gNB 220. For reflective mapping, the SDAP 225 at the gNB 220 maymark the downlink packets with a QoS flow indicator (QFI), which may beobserved by the SDAP 215 at the UE 210 to determine themapping/de-mapping between the QoS flows and the data radio bearers.

The PDCPs 214 and 224 may perform header compression/decompression toreduce the amount of data that needs to be transmitted over the airinterface, ciphering/deciphering to prevent unauthorized decoding ofdata transmitted over the air interface, and integrity protection (toensure control messages originate from intended sources. The PDCPs 214and 224 may perform retransmissions of undelivered packets, in-sequencedelivery and reordering of packets, and removal of packets received induplicate due to, for example, an intra-gNB handover. The PDCPs 214 and224 may perform packet duplication to improve the likelihood of thepacket being received and, at the receiver, remove any duplicatepackets. Packet duplication may be useful for services that require highreliability.

Although not shown in FIG. 3, PDCPs 214 and 224 may performmapping/de-mapping between a split radio bearer and RLC channels in adual connectivity scenario. Dual connectivity is a technique that allowsa UE to connect to two cells or, more generally, two cell groups: amaster cell group (MCG) and a secondary cell group (SCG). A split beareris when a single radio bearer, such as one of the radio bearers providedby the PDCPs 214 and 224 as a service to the SDAPs 215 and 225, ishandled by cell groups in dual connectivity. The PDCPs 214 and 224 maymap/de-map the split radio bearer between RLC channels belonging to cellgroups.

The RLCs 213 and 223 may perform segmentation, retransmission throughAutomatic Repeat Request (ARQ), and removal of duplicate data unitsreceived from MACs 212 and 222, respectively. The RLCs 213 and 223 maysupport three transmission modes: transparent mode (TM); unacknowledgedmode (UM); and acknowledged mode (AM). Based on the transmission mode anRLC is operating, the RLC may perform one or more of the notedfunctions. The RLC configuration may be per logical channel with nodependency on numerologies and/or Transmission Time Interval (TTI)durations. As shown in FIG. 3, the RLCs 213 and 223 may provide RLCchannels as a service to PDCPs 214 and 224, respectively.

The MACs 212 and 222 may perform multiplexing/demultiplexing of logicalchannels and/or mapping between logical channels and transport channels.The multiplexing/demultiplexing may include multiplexing/demultiplexingof data units, belonging to the one or more logical channels, into/fromTransport Blocks (TBs) delivered to/from the PHYs 211 and 221. The MAC222 may be configured to perform scheduling, scheduling informationreporting, and priority handling between UEs by means of dynamicscheduling. Scheduling may be performed in the gNB 220 (at the MAC 222)for downlink and uplink. The MACs 212 and 222 may be configured toperform error correction through Hybrid Automatic Repeat Request (HARQ)(e.g., one HARQ entity per carrier in case of Carrier Aggregation (CA)),priority handling between logical channels of the UE 210 by means oflogical channel prioritization, and/or padding. The MACs 212 and 222 maysupport one or more numerologies and/or transmission timings. In anexample, mapping restrictions in a logical channel prioritization maycontrol which numerology and/or transmission timing a logical channelmay use. As shown in FIG. 3, the MACs 212 and 222 may provide logicalchannels as a service to the RLCs 213 and 223.

The PHYs 211 and 221 may perform mapping of transport channels tophysical channels and digital and analog signal processing functions forsending and receiving information over the air interface. These digitaland analog signal processing functions may include, for example,coding/decoding and modulation/demodulation. The PHYs 211 and 221 mayperform multi-antenna mapping. As shown in FIG. 3, the PHYs 211 and 221may provide one or more transport channels as a service to the MACs 212and 222.

FIG. 4A illustrates an example downlink data flow through the NR userplane protocol stack. FIG. 4A illustrates a downlink data flow of threeIP packets (n, n+1, and m) through the NR user plane protocol stack togenerate two TBs at the gNB 220. An uplink data flow through the NR userplane protocol stack may be similar to the downlink data flow depictedin FIG. 4A.

The downlink data flow of FIG. 4A begins when SDAP 225 receives thethree IP packets from one or more QoS flows and maps the three packetsto radio bearers. In FIG. 4A, the SDAP 225 maps IP packets n and n+1 toa first radio bearer 402 and maps IP packet m to a second radio bearer404. An SDAP header (labeled with an “H” in FIG. 4A) is added to an IPpacket. The data unit from/to a higher protocol layer is referred to asa service data unit (SDU) of the lower protocol layer and the data unitto/from a lower protocol layer is referred to as a protocol data unit(PDU) of the higher protocol layer. As shown in FIG. 4A, the data unitfrom the SDAP 225 is an SDU of lower protocol layer PDCP 224 and is aPDU of the SDAP 225.

The remaining protocol layers in FIG. 4A may perform their associatedfunctionality (e.g., with respect to FIG. 3), add corresponding headers,and forward their respective outputs to the next lower layer. Forexample, the PDCP 224 may perform IP-header compression and cipheringand forward its output to the RLC 223. The RLC 223 may optionallyperform segmentation (e.g., as shown for IP packet m in FIG. 4A) andforward its output to the MAC 222. The MAC 222 may multiplex a number ofRLC PDUs and may attach a MAC subheader to an RLC PDU to form atransport block. In NR, the MAC subheaders may be distributed across theMAC PDU, as illustrated in FIG. 4A. In LTE, the MAC subheaders may beentirely located at the beginning of the MAC PDU. The NR MAC PDUstructure may reduce processing time and associated latency because theMAC PDU subheaders may be computed before the full MAC PDU is assembled.

FIG. 4B illustrates an example format of a MAC subheader in a MAC PDU.The MAC subheader includes: an SDU length field for indicating thelength (e.g., in bytes) of the MAC SDU to which the MAC subheadercorresponds; a logical channel identifier (LCID) field for identifyingthe logical channel from which the MAC SDU originated to aid in thedemultiplexing process; a flag (F) for indicating the size of the SDUlength field; and a reserved bit (R) field for future use.

FIG. 4B further illustrates MAC control elements (CEs) inserted into theMAC PDU by a MAC, such as MAC 223 or MAC 222. For example, FIG. 4Billustrates two MAC CEs inserted into the MAC PDU. MAC CEs may beinserted at the beginning of a MAC PDU for downlink transmissions (asshown in FIG. 4B) and at the end of a MAC PDU for uplink transmissions.MAC CEs may be used for in-band control signaling. Example MAC CEsinclude: scheduling-related MAC CEs, such as buffer status reports andpower headroom reports; activation/deactivation MAC CEs, such as thosefor activation/deactivation of PDCP duplication detection, channel stateinformation (CSI) reporting, sounding reference signal (SRS)transmission, and prior configured components; discontinuous reception(DRX) related MAC CEs; timing advance MAC CEs; and random access relatedMAC CEs. A MAC CE may be preceded by a MAC subheader with a similarformat as described for MAC SDUs and may be identified with a reservedvalue in the LCID field that indicates the type of control informationincluded in the MAC CE.

Before describing the NR control plane protocol stack, logical channels,transport channels, and physical channels are first described as well asa mapping between the channel types. One or more of the channels may beused to carry out functions associated with the NR control planeprotocol stack described later below.

FIG. 5A and FIG. 5B illustrate, for downlink and uplink respectively, amapping between logical channels, transport channels, and physicalchannels. Information is passed through channels between the RLC, theMAC, and the PHY of the NR protocol stack. A logical channel may be usedbetween the RLC and the MAC and may be classified as a control channelthat carries control and configuration information in the NR controlplane or as a traffic channel that carries data in the NR user plane. Alogical channel may be classified as a dedicated logical channel that isdedicated to a specific UE or as a common logical channel that may beused by more than one UE. A logical channel may also be defined by thetype of information it carries. The set of logical channels defined byNR include, for example:

-   -   a paging control channel (PCCH) for carrying paging messages        used to page a UE whose location is not known to the network on        a cell level;    -   a broadcast control channel (BCCH) for carrying system        information messages in the form of a master information block        (MIB) and several system information blocks (SIBs), wherein the        system information messages may be used by the UEs to obtain        information about how a cell is configured and how to operate        within the cell;    -   a common control channel (CCCH) for carrying control messages        together with random access;    -   a dedicated control channel (DCCH) for carrying control messages        to/from a specific the UE to configure the UE; and    -   a dedicated traffic channel (DTCH) for carrying user data        to/from a specific the UE.

Transport channels are used between the MAC and PHY layers and may bedefined by how the information they carry is transmitted over the airinterface. The set of transport channels defined by NR include, forexample:

-   -   a paging channel (PCH) for carrying paging messages that        originated from the PCCH;    -   a broadcast channel (BCH) for carrying the MIB from the BCCH;    -   a downlink shared channel (DL-SCH) for carrying downlink data        and signaling messages, including the SIBs from the BCCH;    -   an uplink shared channel (UL-SCH) for carrying uplink data and        signaling messages; and    -   a random access channel (RACH) for allowing a UE to contact the        network without any prior scheduling.

The PHY may use physical channels to pass information between processinglevels of the PHY. A physical channel may have an associated set oftime-frequency resources for carrying the information of one or moretransport channels. The PHY may generate control information to supportthe low-level operation of the PHY and provide the control informationto the lower levels of the PHY via physical control channels, known asL1/L2 control channels. The set of physical channels and physicalcontrol channels defined by NR include, for example:

-   -   a physical broadcast channel (PBCH) for carrying the MIB from        the BCH;    -   a physical downlink shared channel (PDSCH) for carrying downlink        data and signaling messages from the DL-SCH, as well as paging        messages from the PCH;    -   a physical downlink control channel (PDCCH) for carrying        downlink control information (DCI), which may include downlink        scheduling commands, uplink scheduling grants, and uplink power        control commands;    -   a physical uplink shared channel (PUSCH) for carrying uplink        data and signaling messages from the UL-SCH and in some        instances uplink control information (UCI) as described below;    -   a physical uplink control channel (PUCCH) for carrying UCI,        which may include HARQ acknowledgments, channel quality        indicators (CQI), pre-coding matrix indicators (PMI), rank        indicators (RI), and scheduling requests (SR); and    -   a physical random access channel (PRACH) for random access.

Similar to the physical control channels, the physical layer generatesphysical signals to support the low-level operation of the physicallayer. As shown in FIG. 5A and FIG. 5B, the physical layer signalsdefined by NR include: primary synchronization signals (PSS), secondarysynchronization signals (SSS), channel state information referencesignals (CSI-RS), demodulation reference signals (DMRS), soundingreference signals (SRS), and phase-tracking reference signals (PT-RS).These physical layer signals will be described in greater detail below.

FIG. 2B illustrates an example NR control plane protocol stack. As shownin FIG. 2B, the NR control plane protocol stack may use the same/similarfirst four protocol layers as the example NR user plane protocol stack.These four protocol layers include the PHYs 211 and 221, the MACs 212and 222, the RLCs 213 and 223, and the PDCPs 214 and 224. Instead ofhaving the SDAPs 215 and 225 at the top of the stack as in the NR userplane protocol stack, the NR control plane stack has radio resourcecontrols (RRCs) 216 and 226 and NAS protocols 217 and 237 at the top ofthe NR control plane protocol stack.

The NAS protocols 217 and 237 may provide control plane functionalitybetween the UE 210 and the AMF 230 (e.g., the AMF 158A) or, moregenerally, between the UE 210 and the CN. The NAS protocols 217 and 237may provide control plane functionality between the UE 210 and the AMF230 via signaling messages, referred to as NAS messages. There is nodirect path between the UE 210 and the AMF 230 through which the NASmessages can be transported. The NAS messages may be transported usingthe AS of the Uu and NG interfaces. NAS protocols 217 and 237 mayprovide control plane functionality such as authentication, security,connection setup, mobility management, and session management.

The RRCs 216 and 226 may provide control plane functionality between theUE 210 and the gNB 220 or, more generally, between the UE 210 and theRAN. The RRCs 216 and 226 may provide control plane functionalitybetween the UE 210 and the gNB 220 via signaling messages, referred toas RRC messages. RRC messages may be transmitted between the UE 210 andthe RAN using signaling radio bearers and the same/similar PDCP, RLC,MAC, and PHY protocol layers. The MAC may multiplex control-plane anduser-plane data into the same transport block (TB). The RRCs 216 and 226may provide control plane functionality such as: broadcast of systeminformation related to AS and NAS; paging initiated by the CN or theRAN; establishment, maintenance and release of an RRC connection betweenthe UE 210 and the RAN; security functions including key management;establishment, configuration, maintenance and release of signaling radiobearers and data radio bearers; mobility functions; QoS managementfunctions; the UE measurement reporting and control of the reporting;detection of and recovery from radio link failure (RLF); and/or NASmessage transfer. As part of establishing an RRC connection, RRCs 216and 226 may establish an RRC context, which may involve configuringparameters for communication between the UE 210 and the RAN.

FIG. 6 is an example diagram showing RRC state transitions of a UE. TheUE may be the same or similar to the wireless device 106 depicted inFIG. 1A, the UE 210 depicted in FIG. 2A and FIG. 2B, or any otherwireless device described in the present disclosure. As illustrated inFIG. 6, a UE may be in at least one of three RRC states: RRC connected602 (e.g., RRC_CONNECTED), RRC idle 604 (e.g., RRC_IDLE), and RRCinactive 606 (e.g., RRC_INACTIVE).

In RRC connected 602, the UE has an established RRC context and may haveat least one RRC connection with a base station. The base station may besimilar to one of the one or more base stations included in the RAN 104depicted in FIG. 1A, one of the gNBs 160 or ng-eNBs 162 depicted in FIG.1B, the gNB 220 depicted in FIG. 2A and FIG. 2B, or any other basestation described in the present disclosure. The base station with whichthe UE is connected may have the RRC context for the UE. The RRCcontext, referred to as the UE context, may comprise parameters forcommunication between the UE and the base station. These parameters mayinclude, for example: one or more AS contexts; one or more radio linkconfiguration parameters; bearer configuration information (e.g.,relating to a data radio bearer, signaling radio bearer, logicalchannel, QoS flow, and/or PDU session); security information; and/orPHY, MAC, RLC, PDCP, and/or SDAP layer configuration information. Whilein RRC connected 602, mobility of the UE may be managed by the RAN(e.g., the RAN 104 or the NG-RAN 154). The UE may measure the signallevels (e.g., reference signal levels) from a serving cell andneighboring cells and report these measurements to the base stationcurrently serving the UE. The UE's serving base station may request ahandover to a cell of one of the neighboring base stations based on thereported measurements. The RRC state may transition from RRC connected602 to RRC idle 604 through a connection release procedure 608 or to RRCinactive 606 through a connection inactivation procedure 610.

In RRC idle 604, an RRC context may not be established for the UE. InRRC idle 604, the UE may not have an RRC connection with the basestation. While in RRC idle 604, the UE may be in a sleep state for themajority of the time (e.g., to conserve battery power). The UE may wakeup periodically (e.g., once in every discontinuous reception cycle) tomonitor for paging messages from the RAN. Mobility of the UE may bemanaged by the UE through a procedure known as cell reselection. The RRCstate may transition from RRC idle 604 to RRC connected 602 through aconnection establishment procedure 612, which may involve a randomaccess procedure as discussed in greater detail below.

In RRC inactive 606, the RRC context previously established ismaintained in the UE and the base station. This allows for a fasttransition to RRC connected 602 with reduced signaling overhead ascompared to the transition from RRC idle 604 to RRC connected 602. Whilein RRC inactive 606, the UE may be in a sleep state and mobility of theUE may be managed by the UE through cell reselection. The RRC state maytransition from RRC inactive 606 to RRC connected 602 through aconnection resume procedure 614 or to RRC idle 604 though a connectionrelease procedure 616 that may be the same as or similar to connectionrelease procedure 608.

An RRC state may be associated with a mobility management mechanism. InRRC idle 604 and RRC inactive 606, mobility is managed by the UE throughcell reselection. The purpose of mobility management in RRC idle 604 andRRC inactive 606 is to allow the network to be able to notify the UE ofan event via a paging message without having to broadcast the pagingmessage over the entire mobile communications network. The mobilitymanagement mechanism used in RRC idle 604 and RRC inactive 606 may allowthe network to track the UE on a cell-group level so that the pagingmessage may be broadcast over the cells of the cell group that the UEcurrently resides within instead of the entire mobile communicationnetwork. The mobility management mechanisms for RRC idle 604 and RRCinactive 606 track the UE on a cell-group level. They may do so usingdifferent granularities of grouping. For example, there may be threelevels of cell-grouping granularity: individual cells; cells within aRAN area identified by a RAN area identifier (RAI); and cells within agroup of RAN areas, referred to as a tracking area and identified by atracking area identifier (TAI).

Tracking areas may be used to track the UE at the CN level. The CN(e.g., the CN 102 or the 5G-CN 152) may provide the UE with a list ofTAIs associated with a UE registration area. If the UE moves, throughcell reselection, to a cell associated with a TAI not included in thelist of TAIs associated with the UE registration area, the UE mayperform a registration update with the CN to allow the CN to update theUE's location and provide the UE with a new the UE registration area.

RAN areas may be used to track the UE at the RAN level. For a UE in RRCinactive 606 state, the UE may be assigned a RAN notification area. ARAN notification area may comprise one or more cell identities, a listof RAIs, or a list of TAIs. In an example, a base station may belong toone or more RAN notification areas. In an example, a cell may belong toone or more RAN notification areas. If the UE moves, through cellreselection, to a cell not included in the RAN notification areaassigned to the UE, the UE may perform a notification area update withthe RAN to update the UE's RAN notification area.

A base station storing an RRC context for a UE or a last serving basestation of the UE may be referred to as an anchor base station. Ananchor base station may maintain an RRC context for the UE at leastduring a period of time that the UE stays in a RAN notification area ofthe anchor base station and/or during a period of time that the UE staysin RRC inactive 606.

A gNB, such as gNBs 160 in FIG. 1B, may be split in two parts: a centralunit (gNB-CU), and one or more distributed units (gNB-DU). A gNB-CU maybe coupled to one or more gNB-DUs using an F1 interface. The gNB-CU maycomprise the RRC, the PDCP, and the SDAP. A gNB-DU may comprise the RLC,the MAC, and the PHY.

In NR, the physical signals and physical channels (discussed withrespect to FIG. 5A and FIG. 5B) may be mapped onto orthogonal frequencydivisional multiplexing (OFDM) symbols. OFDM is a multicarriercommunication scheme that transmits data over F orthogonal subcarriers(or tones). Before transmission, the data may be mapped to a series ofcomplex symbols (e.g., M-quadrature amplitude modulation (M-QAM) orM-phase shift keying (M-PSK) symbols), referred to as source symbols,and divided into F parallel symbol streams. The F parallel symbolstreams may be treated as though they are in the frequency domain andused as inputs to an Inverse Fast Fourier Transform (IFFT) block thattransforms them into the time domain. The IFFT block may take in Fsource symbols at a time, one from each of the F parallel symbolstreams, and use each source symbol to modulate the amplitude and phaseof one of F sinusoidal basis functions that correspond to the Forthogonal subcarriers. The output of the IFFT block may be Ftime-domain samples that represent the summation of the F orthogonalsubcarriers. The F time-domain samples may form a single OFDM symbol.After some processing (e.g., addition of a cyclic prefix) andup-conversion, an OFDM symbol provided by the IFFT block may betransmitted over the air interface on a carrier frequency. The Fparallel symbol streams may be mixed using an FFT block before beingprocessed by the IFFT block. This operation produces Discrete FourierTransform (DFT)-precoded OFDM symbols and may be used by UEs in theuplink to reduce the peak to average power ratio (PAPR). Inverseprocessing may be performed on the OFDM symbol at a receiver using anFFT block to recover the data mapped to the source symbols.

FIG. 7 illustrates an example configuration of an NR frame into whichOFDM symbols are grouped. An NR frame may be identified by a systemframe number (SFN). The SFN may repeat with a period of 1024 frames. Asillustrated, one NR frame may be 10 milliseconds (ms) in duration andmay include 10 subframes that are 1 ms in duration. A subframe may bedivided into slots that include, for example, 14 OFDM symbols per slot.

The duration of a slot may depend on the numerology used for the OFDMsymbols of the slot. In NR, a flexible numerology is supported toaccommodate different cell deployments (e.g., cells with carrierfrequencies below 1 GHz up to cells with carrier frequencies in themm-wave range). A numerology may be defined in terms of subcarrierspacing and cyclic prefix duration. For a numerology in NR, subcarrierspacings may be scaled up by powers of two from a baseline subcarrierspacing of 15 kHz, and cyclic prefix durations may be scaled down bypowers of two from a baseline cyclic prefix duration of 4.7 μs. Forexample, NR defines numerologies with the following subcarrierspacing/cyclic prefix duration combinations: 15 kHz/4.7 μs; 30 kHz/2.3μs; 60 kHz/1.2 μs; 120 kHz/0.59 μs; and 240 kHz/0.29 μs.

A slot may have a fixed number of OFDM symbols (e.g., 14 OFDM symbols).A numerology with a higher subcarrier spacing has a shorter slotduration and, correspondingly, more slots per subframe. FIG. 7illustrates this numerology-dependent slot duration andslots-per-subframe transmission structure (the numerology with asubcarrier spacing of 240 kHz is not shown in FIG. 7 for ease ofillustration). A subframe in NR may be used as a numerology-independenttime reference, while a slot may be used as the unit upon which uplinkand downlink transmissions are scheduled. To support low latency,scheduling in NR may be decoupled from the slot duration and start atany OFDM symbol and last for as many symbols as needed for atransmission. These partial slot transmissions may be referred to asmini-slot or subslot transmissions.

FIG. 8 illustrates an example configuration of a slot in the time andfrequency domain for an NR carrier. The slot includes resource elements(REs) and resource blocks (RBs). An RE is the smallest physical resourcein NR. An RE spans one OFDM symbol in the time domain by one subcarrierin the frequency domain as shown in FIG. 8. An RB spans twelveconsecutive REs in the frequency domain as shown in FIG. 8. An NRcarrier may be limited to a width of 275 RBs or 275×12=3300 subcarriers.Such a limitation, if used, may limit the NR carrier to 50, 100, 200,and 400 MHz for subcarrier spacings of 15, 30, 60, and 120 kHz,respectively, where the 400 MHz bandwidth may be set based on a 400 MHzper carrier bandwidth limit.

FIG. 8 illustrates a single numerology being used across the entirebandwidth of the NR carrier. In other example configurations, multiplenumerologies may be supported on the same carrier.

NR may support wide carrier bandwidths (e.g., up to 400 MHz for asubcarrier spacing of 120 kHz). Not all UEs may be able to receive thefull carrier bandwidth (e.g., due to hardware limitations). Also,receiving the full carrier bandwidth may be prohibitive in terms of UEpower consumption. In an example, to reduce power consumption and/or forother purposes, a UE may adapt the size of the UE's receive bandwidthbased on the amount of traffic the UE is scheduled to receive. This isreferred to as bandwidth adaptation.

NR defines bandwidth parts (BWPs) to support UEs not capable ofreceiving the full carrier bandwidth and to support bandwidthadaptation. In an example, a BWP may be defined by a subset ofcontiguous RBs on a carrier. A UE may be configured (e.g., via RRClayer) with one or more downlink BWPs and one or more uplink BWPs perserving cell (e.g., up to four downlink BWPs and up to four uplink BWPsper serving cell). At a given time, one or more of the configured BWPsfor a serving cell may be active. These one or more BWPs may be referredto as active BWPs of the serving cell. When a serving cell is configuredwith a secondary uplink carrier, the serving cell may have one or morefirst active BWPs in the uplink carrier and one or more second activeBWPs in the secondary uplink carrier.

For unpaired spectra, a downlink BWP from a set of configured downlinkBWPs may be linked with an uplink BWP from a set of configured uplinkBWPs if a downlink BWP index of the downlink BWP and an uplink BWP indexof the uplink BWP are the same. For unpaired spectra, a UE may expectthat a center frequency for a downlink BWP is the same as a centerfrequency for an uplink BWP.

For a downlink BWP in a set of configured downlink BWPs on a primarycell (PCell), a base station may configure a UE with one or more controlresource sets (CORESETs) for at least one search space. A search spaceis a set of locations in the time and frequency domains where the UE mayfind control information. The search space may be a UE-specific searchspace or a common search space (potentially usable by a plurality ofUEs). For example, a base station may configure a UE with a commonsearch space, on a PCell or on a primary secondary cell (PSCell), in anactive downlink BWP.

For an uplink BWP in a set of configured uplink BWPs, a BS may configurea UE with one or more resource sets for one or more PUCCH transmissions.A UE may receive downlink receptions (e.g., PDCCH or PDSCH) in adownlink BWP according to a configured numerology (e.g., subcarrierspacing and cyclic prefix duration) for the downlink BWP. The UE maytransmit uplink transmissions (e.g., PUCCH or PUSCH) in an uplink BWPaccording to a configured numerology (e.g., subcarrier spacing andcyclic prefix length for the uplink BWP).

One or more BWP indicator fields may be provided in Downlink ControlInformation (DCI). A value of a BWP indicator field may indicate whichBWP in a set of configured BWPs is an active downlink BWP for one ormore downlink receptions. The value of the one or more BWP indicatorfields may indicate an active uplink BWP for one or more uplinktransmissions.

A base station may semi-statically configure a UE with a defaultdownlink BWP within a set of configured downlink BWPs associated with aPCell. If the base station does not provide the default downlink BWP tothe UE, the default downlink BWP may be an initial active downlink BWP.The UE may determine which BWP is the initial active downlink BWP basedon a CORESET configuration obtained using the PBCH.

A base station may configure a UE with a BWP inactivity timer value fora PCell. The UE may start or restart a BWP inactivity timer at anyappropriate time. For example, the UE may start or restart the BWPinactivity timer (a) when the UE detects a DCI indicating an activedownlink BWP other than a default downlink BWP for a paired spectraoperation; or (b) when a UE detects a DCI indicating an active downlinkBWP or active uplink BWP other than a default downlink BWP or uplink BWPfor an unpaired spectra operation. If the UE does not detect DCI duringan interval of time (e.g., 1 ms or 0.5 ms), the UE may run the BWPinactivity timer toward expiration (for example, increment from zero tothe BWP inactivity timer value, or decrement from the BWP inactivitytimer value to zero). When the BWP inactivity timer expires, the UE mayswitch from the active downlink BWP to the default downlink BWP.

In an example, a base station may semi-statically configure a UE withone or more BWPs. A UE may switch an active BWP from a first BWP to asecond BWP in response to receiving a DCI indicating the second BWP asan active BWP and/or in response to an expiry of the BWP inactivitytimer (e.g., if the second BWP is the default BWP).

Downlink and uplink BWP switching (where BWP switching refers toswitching from a currently active BWP to a not currently active BWP) maybe performed independently in paired spectra. In unpaired spectra,downlink and uplink BWP switching may be performed simultaneously.Switching between configured BWPs may occur based on RRC signaling, DCI,expiration of a BWP inactivity timer, and/or an initiation of randomaccess.

FIG. 9 illustrates an example of bandwidth adaptation using threeconfigured BWPs for an NR carrier. A UE configured with the three BWPsmay switch from one BWP to another BWP at a switching point. In theexample illustrated in FIG. 9, the BWPs include: a BWP 902 with abandwidth of 40 MHz and a subcarrier spacing of 15 kHz; a BWP 904 with abandwidth of 10 MHz and a subcarrier spacing of 15 kHz; and a BWP 906with a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. The BWP902 may be an initial active BWP, and the BWP 904 may be a default BWP.The UE may switch between BWPs at switching points. In the example ofFIG. 9, the UE may switch from the BWP 902 to the BWP 904 at a switchingpoint 908. The switching at the switching point 908 may occur for anysuitable reason, for example, in response to an expiry of a BWPinactivity timer (indicating switching to the default BWP) and/or inresponse to receiving a DCI indicating BWP 904 as the active BWP. The UEmay switch at a switching point 910 from active BWP 904 to BWP 906 inresponse receiving a DCI indicating BWP 906 as the active BWP. The UEmay switch at a switching point 912 from active BWP 906 to BWP 904 inresponse to an expiry of a BWP inactivity timer and/or in responsereceiving a DCI indicating BWP 904 as the active BWP. The UE may switchat a switching point 914 from active BWP 904 to BWP 902 in responsereceiving a DCI indicating BWP 902 as the active BWP.

If a UE is configured for a secondary cell with a default downlink BWPin a set of configured downlink BWPs and a timer value, UE proceduresfor switching BWPs on a secondary cell may be the same/similar as thoseon a primary cell. For example, the UE may use the timer value and thedefault downlink BWP for the secondary cell in the same/similar manneras the UE would use these values for a primary cell.

To provide for greater data rates, two or more carriers can beaggregated and simultaneously transmitted to/from the same UE usingcarrier aggregation (CA). The aggregated carriers in CA may be referredto as component carriers (CCs). When CA is used, there are a number ofserving cells for the UE, one for a CC. The CCs may have threeconfigurations in the frequency domain.

FIG. 10A illustrates the three CA configurations with two CCs. In theintraband, contiguous configuration 1002, the two CCs are aggregated inthe same frequency band (frequency band A) and are located directlyadjacent to each other within the frequency band. In the intraband,non-contiguous configuration 1004, the two CCs are aggregated in thesame frequency band (frequency band A) and are separated in thefrequency band by a gap. In the interband configuration 1006, the twoCCs are located in frequency bands (frequency band A and frequency bandB).

In an example, up to 32 CCs may be aggregated. The aggregated CCs mayhave the same or different bandwidths, subcarrier spacing, and/orduplexing schemes (TDD or FDD). A serving cell for a UE using CA mayhave a downlink CC. For FDD, one or more uplink CCs may be optionallyconfigured for a serving cell. The ability to aggregate more downlinkcarriers than uplink carriers may be useful, for example, when the UEhas more data traffic in the downlink than in the uplink.

When CA is used, one of the aggregated cells for a UE may be referred toas a primary cell (PCell). The PCell may be the serving cell that the UEinitially connects to at RRC connection establishment, reestablishment,and/or handover. The PCell may provide the UE with NAS mobilityinformation and the security input. UEs may have different PCells. Inthe downlink, the carrier corresponding to the PCell may be referred toas the downlink primary CC (DL PCC). In the uplink, the carriercorresponding to the PCell may be referred to as the uplink primary CC(UL PCC). The other aggregated cells for the UE may be referred to assecondary cells (SCells). In an example, the SCells may be configuredafter the PCell is configured for the UE. For example, an SCell may beconfigured through an RRC Connection Reconfiguration procedure. In thedownlink, the carrier corresponding to an SCell may be referred to as adownlink secondary CC (DL SCC). In the uplink, the carrier correspondingto the SCell may be referred to as the uplink secondary CC (UL SCC).

Configured SCells for a UE may be activated and deactivated based on,for example, traffic and channel conditions. Deactivation of an SCellmay mean that PDCCH and PDSCH reception on the SCell is stopped andPUSCH, SRS, and CQI transmissions on the SCell are stopped. ConfiguredSCells may be activated and deactivated using a MAC CE with respect toFIG. 4B. For example, a MAC CE may use a bitmap (e.g., one bit perSCell) to indicate which SCells (e.g., in a subset of configured SCells)for the UE are activated or deactivated. Configured SCells may bedeactivated in response to an expiration of an SCell deactivation timer(e.g., one SCell deactivation timer per SCell).

Downlink control information, such as scheduling assignments andscheduling grants, for a cell may be transmitted on the cellcorresponding to the assignments and grants, which is known asself-scheduling. The DCI for the cell may be transmitted on anothercell, which is known as cross-carrier scheduling. Uplink controlinformation (e.g., HARQ acknowledgments and channel state feedback, suchas CQI, PMI, and/or RI) for aggregated cells may be transmitted on thePUCCH of the PCell. For a larger number of aggregated downlink CCs, thePUCCH of the PCell may become overloaded. Cells may be divided intomultiple PUCCH groups.

FIG. 10B illustrates an example of how aggregated cells may beconfigured into one or more PUCCH groups. A PUCCH group 1010 and a PUCCHgroup 1050 may include one or more downlink CCs, respectively. In theexample of FIG. 10B, the PUCCH group 1010 includes three downlink CCs: aPCell 1011, an SCell 1012, and an SCell 1013. The PUCCH group 1050includes three downlink CCs in the present example: a PCell 1051, anSCell 1052, and an SCell 1053. One or more uplink CCs may be configuredas a PCell 1021, an SCell 1022, and an SCell 1023. One or more otheruplink CCs may be configured as a primary Scell (PSCell) 1061, an SCell1062, and an SCell 1063. Uplink control information (UCI) related to thedownlink CCs of the PUCCH group 1010, shown as UCI 1031, UCI 1032, andUCI 1033, may be transmitted in the uplink of the PCell 1021. Uplinkcontrol information (UCI) related to the downlink CCs of the PUCCH group1050, shown as UCI 1071, UCI 1072, and UCI 1073, may be transmitted inthe uplink of the PSCell 1061. In an example, if the aggregated cellsdepicted in FIG. 10B were not divided into the PUCCH group 1010 and thePUCCH group 1050, a single uplink PCell to transmit UCI relating to thedownlink CCs, and the PCell may become overloaded. By dividingtransmissions of UCI between the PCell 1021 and the PSCell 1061,overloading may be prevented.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned with a physical cell ID and a cell index. The physicalcell ID or the cell index may identify a downlink carrier and/or anuplink carrier of the cell, for example, depending on the context inwhich the physical cell ID is used. A physical cell ID may be determinedusing a synchronization signal transmitted on a downlink componentcarrier. A cell index may be determined using RRC messages. In thedisclosure, a physical cell ID may be referred to as a carrier ID, and acell index may be referred to as a carrier index. For example, when thedisclosure refers to a first physical cell ID for a first downlinkcarrier, the disclosure may mean the first physical cell ID is for acell comprising the first downlink carrier. The same/similar concept mayapply to, for example, a carrier activation. When the disclosureindicates that a first carrier is activated, the specification may meanthat a cell comprising the first carrier is activated.

In CA, a multi-carrier nature of a PHY may be exposed to a MAC. In anexample, a HARQ entity may operate on a serving cell. A transport blockmay be generated per assignment/grant per serving cell. A transportblock and potential HARQ retransmissions of the transport block may bemapped to a serving cell.

In the downlink, a base station may transmit (e.g., unicast, multicast,and/or broadcast) one or more Reference Signals (RSs) to a UE (e.g.,PSS, SSS, CSI-RS, DMRS, and/or PT-RS, as shown in FIG. 5A). In theuplink, the UE may transmit one or more RSs to the base station (e.g.,DMRS, PT-RS, and/or SRS, as shown in FIG. 5B). The PSS and the SSS maybe transmitted by the base station and used by the UE to synchronize theUE to the base station. The PSS and the SSS may be provided in asynchronization signal (SS)/physical broadcast channel (PBCH) block thatincludes the PSS, the SSS, and the PBCH. The base station mayperiodically transmit a burst of SS/PBCH blocks.

FIG. 11A illustrates an example of an SS/PBCH block's structure andlocation. A burst of SS/PBCH blocks may include one or more SS/PBCHblocks (e.g., 4 SS/PBCH blocks, as shown in FIG. 11A). Bursts may betransmitted periodically (e.g., every 2 frames or 20 ms). A burst may berestricted to a half-frame (e.g., a first half-frame having a durationof 5 ms). It will be understood that FIG. 11A is an example, and thatthese parameters (number of SS/PBCH blocks per burst, periodicity ofbursts, position of burst within the frame) may be configured based on,for example: a carrier frequency of a cell in which the SS/PBCH block istransmitted; a numerology or subcarrier spacing of the cell; aconfiguration by the network (e.g., using RRC signaling); or any othersuitable factor. In an example, the UE may assume a subcarrier spacingfor the SS/PBCH block based on the carrier frequency being monitored,unless the radio network configured the UE to assume a differentsubcarrier spacing.

The SS/PBCH block may span one or more OFDM symbols in the time domain(e.g., 4 OFDM symbols, as shown in the example of FIG. 11A) and may spanone or more subcarriers in the frequency domain (e.g., 240 contiguoussubcarriers). The PSS, the SSS, and the PBCH may have a common centerfrequency. The PSS may be transmitted first and may span, for example, 1OFDM symbol and 127 subcarriers. The SSS may be transmitted after thePSS (e.g., two symbols later) and may span 1 OFDM symbol and 127subcarriers. The PBCH may be transmitted after the PSS (e.g., across thenext 3 OFDM symbols) and may span 240 subcarriers.

The location of the SS/PBCH block in the time and frequency domains maynot be known to the UE (e.g., if the UE is searching for the cell). Tofind and select the cell, the UE may monitor a carrier for the PSS. Forexample, the UE may monitor a frequency location within the carrier. Ifthe PSS is not found after a certain duration (e.g., 20 ms), the UE maysearch for the PSS at a different frequency location within the carrier,as indicated by a synchronization raster. If the PSS is found at alocation in the time and frequency domains, the UE may determine, basedon a known structure of the SS/PBCH block, the locations of the SSS andthe PBCH, respectively. The SS/PBCH block may be a cell-defining SSblock (CD-SSB). In an example, a primary cell may be associated with aCD-SSB. The CD-SSB may be located on a synchronization raster. In anexample, a cell selection/search and/or reselection may be based on theCD-SSB.

The SS/PBCH block may be used by the UE to determine one or moreparameters of the cell. For example, the UE may determine a physicalcell identifier (PCI) of the cell based on the sequences of the PSS andthe SSS, respectively. The UE may determine a location of a frameboundary of the cell based on the location of the SS/PBCH block. Forexample, the SS/PBCH block may indicate that it has been transmitted inaccordance with a transmission pattern, wherein a SS/PBCH block in thetransmission pattern is a known distance from the frame boundary.

The PBCH may use a QPSK modulation and may use forward error correction(FEC). The FEC may use polar coding. One or more symbols spanned by thePBCH may carry one or more DMRSs for demodulation of the PBCH. The PBCHmay include an indication of a current system frame number (SFN) of thecell and/or a SS/PBCH block timing index. These parameters mayfacilitate time synchronization of the UE to the base station. The PBCHmay include a master information block (MIB) used to provide the UE withone or more parameters. The MIB may be used by the UE to locateremaining minimum system information (RMSI) associated with the cell.The RMSI may include a System Information Block Type 1 (SIB1). The SIB1may contain information needed by the UE to access the cell. The UE mayuse one or more parameters of the MIB to monitor PDCCH, which may beused to schedule PDSCH. The PDSCH may include the SIB1. The SIB1 may bedecoded using parameters provided in the MIB. The PBCH may indicate anabsence of SIB1. Based on the PBCH indicating the absence of SIB1, theUE may be pointed to a frequency. The UE may search for an SS/PBCH blockat the frequency to which the UE is pointed.

The UE may assume that one or more SS/PBCH blocks transmitted with asame SS/PBCH block index are quasi co-located (QCLed) (e.g., having thesame/similar Doppler spread, Doppler shift, average gain, average delay,and/or spatial Rx parameters). The UE may not assume QCL for SS/PBCHblock transmissions having different SS/PBCH block indices.

SS/PBCH blocks (e.g., those within a half-frame) may be transmitted inspatial directions (e.g., using different beams that span a coveragearea of the cell). In an example, a first SS/PBCH block may betransmitted in a first spatial direction using a first beam, and asecond SS/PBCH block may be transmitted in a second spatial directionusing a second beam.

In an example, within a frequency span of a carrier, a base station maytransmit a plurality of SS/PBCH blocks. In an example, a first PCI of afirst SS/PBCH block of the plurality of SS/PBCH blocks may be differentfrom a second PCI of a second SS/PBCH block of the plurality of SS/PBCHblocks. The PCIs of SS/PBCH blocks transmitted in different frequencylocations may be different or the same.

The CSI-RS may be transmitted by the base station and used by the UE toacquire channel state information (CSI). The base station may configurethe UE with one or more CSI-RSs for channel estimation or any othersuitable purpose. The base station may configure a UE with one or moreof the same/similar CSI-RSs. The UE may measure the one or more CSI-RSs.The UE may estimate a downlink channel state and/or generate a CSIreport based on the measuring of the one or more downlink CSI-RSs. TheUE may provide the CSI report to the base station. The base station mayuse feedback provided by the UE (e.g., the estimated downlink channelstate) to perform link adaptation.

The base station may semi-statically configure the UE with one or moreCSI-RS resource sets. A CSI-RS resource may be associated with alocation in the time and frequency domains and a periodicity. The basestation may selectively activate and/or deactivate a CSI-RS resource.The base station may indicate to the UE that a CSI-RS resource in theCSI-RS resource set is activated and/or deactivated.

The base station may configure the UE to report CSI measurements. Thebase station may configure the UE to provide CSI reports periodically,aperiodically, or semi-persistently. For periodic CSI reporting, the UEmay be configured with a timing and/or periodicity of a plurality of CSIreports. For aperiodic CSI reporting, the base station may request a CSIreport. For example, the base station may command the UE to measure aconfigured CSI-RS resource and provide a CSI report relating to themeasurements. For semi-persistent CSI reporting, the base station mayconfigure the UE to transmit periodically, and selectively activate ordeactivate the periodic reporting. The base station may configure the UEwith a CSI-RS resource set and CSI reports using RRC signaling.

The CSI-RS configuration may comprise one or more parameters indicating,for example, up to 32 antenna ports. The UE may be configured to employthe same OFDM symbols for a downlink CSI-RS and a control resource set(CORESET) when the downlink CSI-RS and CORESET are spatially QCLed andresource elements associated with the downlink CSI-RS are outside of thephysical resource blocks (PRBs) configured for the CORESET. The UE maybe configured to employ the same OFDM symbols for downlink CSI-RS andSS/PBCH blocks when the downlink CSI-RS and SS/PBCH blocks are spatiallyQCLed and resource elements associated with the downlink CSI-RS areoutside of PRBs configured for the SS/PBCH blocks.

Downlink DMRSs may be transmitted by a base station and used by a UE forchannel estimation. For example, the downlink DMRS may be used forcoherent demodulation of one or more downlink physical channels (e.g.,PDSCH). An NR network may support one or more variable and/orconfigurable DMRS patterns for data demodulation. At least one downlinkDMRS configuration may support a front-loaded DMRS pattern. Afront-loaded DMRS may be mapped over one or more OFDM symbols (e.g., oneor two adjacent OFDM symbols). A base station may semi-staticallyconfigure the UE with a number (e.g. a maximum number) of front-loadedDMRS symbols for PDSCH. A DMRS configuration may support one or moreDMRS ports. For example, for single user-MIMO, a DMRS configuration maysupport up to eight orthogonal downlink DMRS ports per UE. Formultiuser-MIMO, a DMRS configuration may support up to 4 orthogonaldownlink DMRS ports per UE. A radio network may support (e.g., at leastfor CP-OFDM) a common DMRS structure for downlink and uplink, wherein aDMRS location, a DMRS pattern, and/or a scrambling sequence may be thesame or different. The base station may transmit a downlink DMRS and acorresponding PDSCH using the same precoding matrix. The UE may use theone or more downlink DMRSs for coherent demodulation/channel estimationof the PDSCH.

In an example, a transmitter (e.g., a base station) may use a precodermatrices for a part of a transmission bandwidth. For example, thetransmitter may use a first precoder matrix for a first bandwidth and asecond precoder matrix for a second bandwidth. The first precoder matrixand the second precoder matrix may be different based on the firstbandwidth being different from the second bandwidth. The UE may assumethat a same precoding matrix is used across a set of PRBs. The set ofPRBs may be denoted as a precoding resource block group (PRG).

A PDSCH may comprise one or more layers. The UE may assume that at leastone symbol with DMRS is present on a layer of the one or more layers ofthe PDSCH. A higher layer may configure up to 3 DMRSs for the PDSCH.

Downlink PT-RS may be transmitted by a base station and used by a UE forphase-noise compensation. Whether a downlink PT-RS is present or not maydepend on an RRC configuration. The presence and/or pattern of thedownlink PT-RS may be configured on a UE-specific basis using acombination of RRC signaling and/or an association with one or moreparameters employed for other purposes (e.g., modulation and codingscheme (MCS)), which may be indicated by DCI. When configured, a dynamicpresence of a downlink PT-RS may be associated with one or more DCIparameters comprising at least MCS. An NR network may support aplurality of PT-RS densities defined in the time and/or frequencydomains. When present, a frequency domain density may be associated withat least one configuration of a scheduled bandwidth. The UE may assume asame precoding for a DMRS port and a PT-RS port. A number of PT-RS portsmay be fewer than a number of DMRS ports in a scheduled resource.Downlink PT-RS may be confined in the scheduled time/frequency durationfor the UE. Downlink PT-RS may be transmitted on symbols to facilitatephase tracking at the receiver.

The UE may transmit an uplink DMRS to a base station for channelestimation. For example, the base station may use the uplink DMRS forcoherent demodulation of one or more uplink physical channels. Forexample, the UE may transmit an uplink DMRS with a PUSCH and/or a PUCCH.The uplink DM-RS may span a range of frequencies that is similar to arange of frequencies associated with the corresponding physical channel.The base station may configure the UE with one or more uplink DMRSconfigurations. At least one DMRS configuration may support afront-loaded DMRS pattern. The front-loaded DMRS may be mapped over oneor more OFDM symbols (e.g., one or two adjacent OFDM symbols). One ormore uplink DMRSs may be configured to transmit at one or more symbolsof a PUSCH and/or a PUCCH. The base station may semi-staticallyconfigure the UE with a number (e.g. maximum number) of front-loadedDMRS symbols for the PUSCH and/or the PUCCH, which the UE may use toschedule a single-symbol DMRS and/or a double-symbol DMRS. An NR networkmay support (e.g., for cyclic prefix orthogonal frequency divisionmultiplexing (CP-OFDM)) a common DMRS structure for downlink and uplink,wherein a DMRS location, a DMRS pattern, and/or a scrambling sequencefor the DMRS may be the same or different.

A PUSCH may comprise one or more layers, and the UE may transmit atleast one symbol with DMRS present on a layer of the one or more layersof the PUSCH. In an example, a higher layer may configure up to threeDMRSs for the PUSCH.

Uplink PT-RS (which may be used by a base station for phase trackingand/or phase-noise compensation) may or may not be present depending onan RRC configuration of the UE. The presence and/or pattern of uplinkPT-RS may be configured on a UE-specific basis by a combination of RRCsignaling and/or one or more parameters employed for other purposes(e.g., Modulation and Coding Scheme (MCS)), which may be indicated byDCI. When configured, a dynamic presence of uplink PT-RS may beassociated with one or more DCI parameters comprising at least MCS. Aradio network may support a plurality of uplink PT-RS densities definedin time/frequency domain. When present, a frequency domain density maybe associated with at least one configuration of a scheduled bandwidth.The UE may assume a same precoding for a DMRS port and a PT-RS port. Anumber of PT-RS ports may be fewer than a number of DMRS ports in ascheduled resource. For example, uplink PT-RS may be confined in thescheduled time/frequency duration for the UE.

SRS may be transmitted by a UE to a base station for channel stateestimation to support uplink channel dependent scheduling and/or linkadaptation. SRS transmitted by the UE may allow a base station toestimate an uplink channel state at one or more frequencies. A schedulerat the base station may employ the estimated uplink channel state toassign one or more resource blocks for an uplink PUSCH transmission fromthe UE. The base station may semi-statically configure the UE with oneor more SRS resource sets. For an SRS resource set, the base station mayconfigure the UE with one or more SRS resources. An SRS resource setapplicability may be configured by a higher layer (e.g., RRC) parameter.For example, when a higher layer parameter indicates beam management, anSRS resource in a SRS resource set of the one or more SRS resource sets(e.g., with the same/similar time domain behavior, periodic, aperiodic,and/or the like) may be transmitted at a time instant (e.g.,simultaneously). The UE may transmit one or more SRS resources in SRSresource sets. An NR network may support aperiodic, periodic and/orsemi-persistent SRS transmissions. The UE may transmit SRS resourcesbased on one or more trigger types, wherein the one or more triggertypes may comprise higher layer signaling (e.g., RRC) and/or one or moreDCI formats. In an example, at least one DCI format may be employed forthe UE to select at least one of one or more configured SRS resourcesets. An SRS trigger type 0 may refer to an SRS triggered based on ahigher layer signaling. An SRS trigger type 1 may refer to an SRStriggered based on one or more DCI formats. In an example, when PUSCHand SRS are transmitted in a same slot, the UE may be configured totransmit SRS after a transmission of a PUSCH and a corresponding uplinkDMRS.

The base station may semi-statically configure the UE with one or moreSRS configuration parameters indicating at least one of following: a SRSresource configuration identifier; a number of SRS ports; time domainbehavior of an SRS resource configuration (e.g., an indication ofperiodic, semi-persistent, or aperiodic SRS); slot, mini-slot, and/orsubframe level periodicity; offset for a periodic and/or an aperiodicSRS resource; a number of OFDM symbols in an SRS resource; a startingOFDM symbol of an SRS resource; an SRS bandwidth; a frequency hoppingbandwidth; a cyclic shift; and/or an SRS sequence ID.

An antenna port is defined such that the channel over which a symbol onthe antenna port is conveyed can be inferred from the channel over whichanother symbol on the same antenna port is conveyed. If a first symboland a second symbol are transmitted on the same antenna port, thereceiver may infer the channel (e.g., fading gain, multipath delay,and/or the like) for conveying the second symbol on the antenna port,from the channel for conveying the first symbol on the antenna port. Afirst antenna port and a second antenna port may be referred to as quasico-located (QCLed) if one or more large-scale properties of the channelover which a first symbol on the first antenna port is conveyed may beinferred from the channel over which a second symbol on a second antennaport is conveyed. The one or more large-scale properties may comprise atleast one of: a delay spread; a Doppler spread; a Doppler shift; anaverage gain; an average delay; and/or spatial Receiving (Rx)parameters.

Channels that use beamforming require beam management. Beam managementmay comprise beam measurement, beam selection, and beam indication. Abeam may be associated with one or more reference signals. For example,a beam may be identified by one or more beamformed reference signals.The UE may perform downlink beam measurement based on downlink referencesignals (e.g., a channel state information reference signal (CSI-RS))and generate a beam measurement report. The UE may perform the downlinkbeam measurement procedure after an RRC connection is set up with a basestation.

FIG. 11B illustrates an example of channel state information referencesignals (CSI-RSs) that are mapped in the time and frequency domains. Asquare shown in FIG. 11B may span a resource block (RB) within abandwidth of a cell. A base station may transmit one or more RRCmessages comprising CSI-RS resource configuration parameters indicatingone or more CSI-RSs. One or more of the following parameters may beconfigured by higher layer signaling (e.g., RRC and/or MAC signaling)for a CSI-RS resource configuration: a CSI-RS resource configurationidentity, a number of CSI-RS ports, a CSI-RS configuration (e.g., symboland resource element (RE) locations in a subframe), a CSI-RS subframeconfiguration (e.g., subframe location, offset, and periodicity in aradio frame), a CSI-RS power parameter, a CSI-RS sequence parameter, acode division multiplexing (CDM) type parameter, a frequency density, atransmission comb, quasi co-location (QCL) parameters (e.g.,QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist,csi-rs-configZPid, qcl-csi-rs-configNZPid), and/or other radio resourceparameters.

The three beams illustrated in FIG. 11B may be configured for a UE in aUE-specific configuration. Three beams are illustrated in FIG. 11B (beam#1, beam #2, and beam #3), more or fewer beams may be configured. Beam#1 may be allocated with CSI-RS 1101 that may be transmitted in one ormore subcarriers in an RB of a first symbol. Beam #2 may be allocatedwith CSI-RS 1102 that may be transmitted in one or more subcarriers inan RB of a second symbol. Beam #3 may be allocated with CSI-RS 1103 thatmay be transmitted in one or more subcarriers in an RB of a thirdsymbol. By using frequency division multiplexing (FDM), a base stationmay use other subcarriers in a same RB (for example, those that are notused to transmit CSI-RS 1101) to transmit another CSI-RS associated witha beam for another UE. By using time domain multiplexing (TDM), beamsused for the UE may be configured such that beams for the UE use symbolsfrom beams of other UEs.

CSI-RSs such as those illustrated in FIG. 11B (e.g., CSI-RS 1101, 1102,1103) may be transmitted by the base station and used by the UE for oneor more measurements. For example, the UE may measure a reference signalreceived power (RSRP) of configured CSI-RS resources. The base stationmay configure the UE with a reporting configuration and the UE mayreport the RSRP measurements to a network (for example, via one or morebase stations) based on the reporting configuration. In an example, thebase station may determine, based on the reported measurement results,one or more transmission configuration indication (TCI) statescomprising a number of reference signals. In an example, the basestation may indicate one or more TCI states to the UE (e.g., via RRCsignaling, a MAC CE, and/or a DCI). The UE may receive a downlinktransmission with a receive (Rx) beam determined based on the one ormore TCI states. In an example, the UE may or may not have a capabilityof beam correspondence. If the UE has the capability of beamcorrespondence, the UE may determine a spatial domain filter of atransmit (Tx) beam based on a spatial domain filter of the correspondingRx beam. If the UE does not have the capability of beam correspondence,the UE may perform an uplink beam selection procedure to determine thespatial domain filter of the Tx beam. The UE may perform the uplink beamselection procedure based on one or more sounding reference signal (SRS)resources configured to the UE by the base station. The base station mayselect and indicate uplink beams for the UE based on measurements of theone or more SRS resources transmitted by the UE.

In a beam management procedure, a UE may assess (e.g., measure) achannel quality of one or more beam pair links, a beam pair linkcomprising a transmitting beam transmitted by a base station and areceiving beam received by the UE. Based on the assessment, the UE maytransmit a beam measurement report indicating one or more beam pairquality parameters comprising, e.g., one or more beam identifications(e.g., a beam index, a reference signal index, or the like), RSRP, aprecoding matrix indicator (PMI), a channel quality indicator (CQI),and/or a rank indicator (RI).

FIG. 12A illustrates examples of three downlink beam managementprocedures: P1, P2, and P3. Procedure P1 may enable a UE measurement ontransmit (Tx) beams of a transmission reception point (TRP) (or multipleTRPs), e.g., to support a selection of one or more base station Tx beamsand/or UE Rx beams (shown as ovals in the top row and bottom row,respectively, of P1). Beamforming at a TRP may comprise a Tx beam sweepfor a set of beams (shown, in the top rows of P1 and P2, as ovalsrotated in a counter-clockwise direction indicated by the dashed arrow).Beamforming at a UE may comprise an Rx beam sweep for a set of beams(shown, in the bottom rows of P1 and P3, as ovals rotated in a clockwisedirection indicated by the dashed arrow). Procedure P2 may be used toenable a UE measurement on Tx beams of a TRP (shown, in the top row ofP2, as ovals rotated in a counter-clockwise direction indicated by thedashed arrow). The UE and/or the base station may perform procedure P2using a smaller set of beams than is used in procedure P1, or usingnarrower beams than the beams used in procedure P1. This may be referredto as beam refinement. The UE may perform procedure P3 for Rx beamdetermination by using the same Tx beam at the base station and sweepingan Rx beam at the UE.

FIG. 12B illustrates examples of three uplink beam managementprocedures: U1, U2, and U3. Procedure U1 may be used to enable a basestation to perform a measurement on Tx beams of a UE, e.g., to support aselection of one or more UE Tx beams and/or base station Rx beams (shownas ovals in the top row and bottom row, respectively, of U1).Beamforming at the UE may include, e.g., a Tx beam sweep from a set ofbeams (shown in the bottom rows of U1 and U3 as ovals rotated in aclockwise direction indicated by the dashed arrow). Beamforming at thebase station may include, e.g., an Rx beam sweep from a set of beams(shown, in the top rows of U1 and U2, as ovals rotated in acounter-clockwise direction indicated by the dashed arrow). Procedure U2may be used to enable the base station to adjust its Rx beam when the UEuses a fixed Tx beam. The UE and/or the base station may performprocedure U2 using a smaller set of beams than is used in procedure P1,or using narrower beams than the beams used in procedure P1. This may bereferred to as beam refinement The UE may perform procedure U3 to adjustits Tx beam when the base station uses a fixed Rx beam.

A UE may initiate a beam failure recovery (BFR) procedure based ondetecting a beam failure. The UE may transmit a BFR request (e.g., apreamble, a UCI, an SR, a MAC CE, and/or the like) based on theinitiating of the BFR procedure. The UE may detect the beam failurebased on a determination that a quality of beam pair link(s) of anassociated control channel is unsatisfactory (e.g., having an error ratehigher than an error rate threshold, a received signal power lower thana received signal power threshold, an expiration of a timer, and/or thelike).

The UE may measure a quality of a beam pair link using one or morereference signals (RSs) comprising one or more SS/PBCH blocks, one ormore CSI-RS resources, and/or one or more demodulation reference signals(DMRSs). A quality of the beam pair link may be based on one or more ofa block error rate (BLER), an RSRP value, a signal to interference plusnoise ratio (SINR) value, a reference signal received quality (RSRQ)value, and/or a CSI value measured on RS resources. The base station mayindicate that an RS resource is quasi co-located (QCLed) with one ormore DM-RSs of a channel (e.g., a control channel, a shared datachannel, and/or the like). The RS resource and the one or more DMRSs ofthe channel may be QCLed when the channel characteristics (e.g., Dopplershift, Doppler spread, average delay, delay spread, spatial Rxparameter, fading, and/or the like) from a transmission via the RSresource to the UE are similar or the same as the channelcharacteristics from a transmission via the channel to the UE.

A network (e.g., a gNB and/or an ng-eNB of a network) and/or the UE mayinitiate a random access procedure. A UE in an RRC_IDLE state and/or anRRC_INACTIVE state may initiate the random access procedure to request aconnection setup to a network. The UE may initiate the random accessprocedure from an RRC_CONNECTED state. The UE may initiate the randomaccess procedure to request uplink resources (e.g., for uplinktransmission of an SR when there is no PUCCH resource available) and/oracquire uplink timing (e.g., when uplink synchronization status isnon-synchronized). The UE may initiate the random access procedure torequest one or more system information blocks (SIBs) (e.g., other systeminformation such as SIB2, SIB3, and/or the like). The UE may initiatethe random access procedure for a beam failure recovery request. Anetwork may initiate a random access procedure for a handover and/or forestablishing time alignment for an SCell addition.

FIG. 13A illustrates a four-step contention-based random accessprocedure. Prior to initiation of the procedure, a base station maytransmit a configuration message 1310 to the UE. The procedureillustrated in FIG. 13A comprises transmission of four messages: a Msg 11311, a Msg 2 1312, a Msg 3 1313, and a Msg 4 1314. The Msg 1 1311 mayinclude and/or be referred to as a preamble (or a random accesspreamble). The Msg 2 1312 may include and/or be referred to as a randomaccess response (RAR).

The configuration message 1310 may be transmitted, for example, usingone or more RRC messages. The one or more RRC messages may indicate oneor more random access channel (RACH) parameters to the UE. The one ormore RACH parameters may comprise at least one of following: generalparameters for one or more random access procedures (e.g.,RACH-configGeneral); cell-specific parameters (e.g., RACH-ConfigCommon);and/or dedicated parameters (e.g., RACH-configDedicated). The basestation may broadcast or multicast the one or more RRC messages to oneor more UEs. The one or more RRC messages may be UE-specific (e.g.,dedicated RRC messages transmitted to a UE in an RRC_CONNECTED stateand/or in an RRC_INACTIVE state). The UE may determine, based on the oneor more RACH parameters, a time-frequency resource and/or an uplinktransmit power for transmission of the Msg 1 1311 and/or the Msg 3 1313.Based on the one or more RACH parameters, the UE may determine areception timing and a downlink channel for receiving the Msg 2 1312 andthe Msg 4 1314.

The one or more RACH parameters provided in the configuration message1310 may indicate one or more Physical RACH (PRACH) occasions availablefor transmission of the Msg 1 1311. The one or more PRACH occasions maybe predefined. The one or more RACH parameters may indicate one or moreavailable sets of one or more PRACH occasions (e.g., prach-ConfigIndex).The one or more RACH parameters may indicate an association between (a)one or more PRACH occasions and (b) one or more reference signals. Theone or more RACH parameters may indicate an association between (a) oneor more preambles and (b) one or more reference signals. The one or morereference signals may be SS/PBCH blocks and/or CSI-RSs. For example, theone or more RACH parameters may indicate a number of SS/PBCH blocksmapped to a PRACH occasion and/or a number of preambles mapped to aSS/PBCH blocks.

The one or more RACH parameters provided in the configuration message1310 may be used to determine an uplink transmit power of Msg 1 1311and/or Msg 3 1313. For example, the one or more RACH parameters mayindicate a reference power for a preamble transmission (e.g., a receivedtarget power and/or an initial power of the preamble transmission).There may be one or more power offsets indicated by the one or more RACHparameters. For example, the one or more RACH parameters may indicate: apower ramping step; a power offset between SSB and CSI-RS; a poweroffset between transmissions of the Msg 1 1311 and the Msg 3 1313;and/or a power offset value between preamble groups. The one or moreRACH parameters may indicate one or more thresholds based on which theUE may determine at least one reference signal (e.g., an SSB and/orCSI-RS) and/or an uplink carrier (e.g., a normal uplink (NUL) carrierand/or a supplemental uplink (SUL) carrier).

The Msg 1 1311 may include one or more preamble transmissions (e.g., apreamble transmission and one or more preamble retransmissions). An RRCmessage may be used to configure one or more preamble groups (e.g.,group A and/or group B). A preamble group may comprise one or morepreambles. The UE may determine the preamble group based on a pathlossmeasurement and/or a size of the Msg 3 1313. The UE may measure an RSRPof one or more reference signals (e.g., SSBs and/or CSI-RSs) anddetermine at least one reference signal having an RSRP above an RSRPthreshold (e.g., rsrp-ThresholdSSB and/or rsrp-ThresholdCSI-RS). The UEmay select at least one preamble associated with the one or morereference signals and/or a selected preamble group, for example, if theassociation between the one or more preambles and the at least onereference signal is configured by an RRC message.

The UE may determine the preamble based on the one or more RACHparameters provided in the configuration message 1310. For example, theUE may determine the preamble based on a pathloss measurement, an RSRPmeasurement, and/or a size of the Msg 3 1313. As another example, theone or more RACH parameters may indicate: a preamble format; a maximumnumber of preamble transmissions; and/or one or more thresholds fordetermining one or more preamble groups (e.g., group A and group B). Abase station may use the one or more RACH parameters to configure the UEwith an association between one or more preambles and one or morereference signals (e.g., SSBs and/or CSI-RSs). If the association isconfigured, the UE may determine the preamble to include in Msg 1 1311based on the association. The Msg 1 1311 may be transmitted to the basestation via one or more PRACH occasions. The UE may use one or morereference signals (e.g., SSBs and/or CSI-RSs) for selection of thepreamble and for determining of the PRACH occasion. One or more RACHparameters (e.g., ra-ssb-OccasionMskIndex and/or ra-OccasionList) mayindicate an association between the PRACH occasions and the one or morereference signals.

The UE may perform a preamble retransmission if no response is receivedfollowing a preamble transmission. The UE may increase an uplinktransmit power for the preamble retransmission. The UE may select aninitial preamble transmit power based on a pathloss measurement and/or atarget received preamble power configured by the network. The UE maydetermine to retransmit a preamble and may ramp up the uplink transmitpower. The UE may receive one or more RACH parameters (e.g.,PREAMBLE_POWER_RAMPING_STEP) indicating a ramping step for the preambleretransmission. The ramping step may be an amount of incrementalincrease in uplink transmit power for a retransmission. The UE may rampup the uplink transmit power if the UE determines a reference signal(e.g., SSB and/or CSI-RS) that is the same as a previous preambletransmission. The UE may count a number of preamble transmissions and/orretransmissions (e.g., PREAMBLE_TRANSMISSION_COUNTER). The UE maydetermine that a random access procedure completed unsuccessfully, forexample, if the number of preamble transmissions exceeds a thresholdconfigured by the one or more RACH parameters (e.g., preambleTransMax).

The Msg 2 1312 received by the UE may include an RAR. In some scenarios,the Msg 2 1312 may include multiple RARs corresponding to multiple UEs.The Msg 2 1312 may be received after or in response to the transmittingof the Msg 1 1311. The Msg 2 1312 may be scheduled on the DL-SCH andindicated on a PDCCH using a random access RNTI (RA-RNTI). The Msg 21312 may indicate that the Msg 1 1311 was received by the base station.The Msg 2 1312 may include a time-alignment command that may be used bythe UE to adjust the UE's transmission timing, a scheduling grant fortransmission of the Msg 3 1313, and/or a Temporary Cell RNTI (TC-RNTI).After transmitting a preamble, the UE may start a time window (e.g.,ra-ResponseWindow) to monitor a PDCCH for the Msg 2 1312. The UE maydetermine when to start the time window based on a PRACH occasion thatthe UE uses to transmit the preamble. For example, the UE may start thetime window one or more symbols after a last symbol of the preamble(e.g., at a first PDCCH occasion from an end of a preambletransmission). The one or more symbols may be determined based on anumerology. The PDCCH may be in a common search space (e.g., aType1-PDCCH common search space) configured by an RRC message. The UEmay identify the RAR based on a Radio Network Temporary Identifier(RNTI). RNTIs may be used depending on one or more events initiating therandom access procedure. The UE may use random access RNTI (RA-RNTI).The RA-RNTI may be associated with PRACH occasions in which the UEtransmits a preamble. For example, the UE may determine the RA-RNTIbased on: an OFDM symbol index; a slot index; a frequency domain index;and/or a UL carrier indicator of the PRACH occasions. An example ofRA-RNTI may be as follows:

RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id

where s_id may be an index of a first OFDM symbol of the PRACH occasion(e.g., 0≤s_id<14), t_id may be an index of a first slot of the PRACHoccasion in a system frame (e.g., 0≤t_id<80), f_id may be an index ofthe PRACH occasion in the frequency domain (e.g., 0≤f_id<8), andul_carrier_id may be a UL carrier used for a preamble transmission(e.g., 0 for an NUL carrier, and 1 for an SUL carrier).

The UE may transmit the Msg 3 1313 in response to a successful receptionof the Msg 2 1312 (e.g., using resources identified in the Msg 2 1312).The Msg 3 1313 may be used for contention resolution in, for example,the contention-based random access procedure illustrated in FIG. 13A. Insome scenarios, a plurality of UEs may transmit a same preamble to abase station and the base station may provide an RAR that corresponds toa UE. Collisions may occur if the plurality of UEs interpret the RAR ascorresponding to themselves. Contention resolution (e.g., using the Msg3 1313 and the Msg 4 1314) may be used to increase the likelihood thatthe UE does not incorrectly use an identity of another the UE. Toperform contention resolution, the UE may include a device identifier inthe Msg 3 1313 (e.g., a C-RNTI if assigned, a TC-RNTI included in theMsg 2 1312, and/or any other suitable identifier).

The Msg 4 1314 may be received after or in response to the transmittingof the Msg 3 1313. If a C-RNTI was included in the Msg 3 1313, the basestation will address the UE on the PDCCH using the C-RNTI. If the UE'sunique C-RNTI is detected on the PDCCH, the random access procedure isdetermined to be successfully completed. If a TC-RNTI is included in theMsg 3 1313 (e.g., if the UE is in an RRC_IDLE state or not otherwiseconnected to the base station), Msg 4 1314 will be received using aDL-SCH associated with the TC-RNTI. If a MAC PDU is successfully decodedand a MAC PDU comprises the UE contention resolution identity MAC CEthat matches or otherwise corresponds with the CCCH SDU sent (e.g.,transmitted) in Msg 3 1313, the UE may determine that the contentionresolution is successful and/or the UE may determine that the randomaccess procedure is successfully completed.

The UE may be configured with a supplementary uplink (SUL) carrier and anormal uplink (NUL) carrier. An initial access (e.g., random accessprocedure) may be supported in an uplink carrier. For example, a basestation may configure the UE with two separate RACH configurations: onefor an SUL carrier and the other for an NUL carrier. For random accessin a cell configured with an SUL carrier, the network may indicate whichcarrier to use (NUL or SUL). The UE may determine the SUL carrier, forexample, if a measured quality of one or more reference signals is lowerthan a broadcast threshold. Uplink transmissions of the random accessprocedure (e.g., the Msg 1 1311 and/or the Msg 3 1313) may remain on theselected carrier. The UE may switch an uplink carrier during the randomaccess procedure (e.g., between the Msg 1 1311 and the Msg 3 1313) inone or more cases. For example, the UE may determine and/or switch anuplink carrier for the Msg 1 1311 and/or the Msg 3 1313 based on achannel clear assessment (e.g., a listen-before-talk).

FIG. 13B illustrates a two-step contention-free random access procedure.Similar to the four-step contention-based random access procedureillustrated in FIG. 13A, a base station may, prior to initiation of theprocedure, transmit a configuration message 1320 to the UE. Theconfiguration message 1320 may be analogous in some respects to theconfiguration message 1310. The procedure illustrated in FIG. 13Bcomprises transmission of two messages: a Msg 1 1321 and a Msg 2 1322.The Msg 1 1321 and the Msg 2 1322 may be analogous in some respects tothe Msg 1 1311 and a Msg 2 1312 illustrated in FIG. 13A, respectively.As will be understood from FIGS. 13A and 13B, the contention-free randomaccess procedure may not include messages analogous to the Msg 3 1313and/or the Msg 4 1314.

The contention-free random access procedure illustrated in FIG. 13B maybe initiated for a beam failure recovery, other SI request, SCelladdition, and/or handover. For example, a base station may indicate orassign to the UE the preamble to be used for the Msg 1 1321. The UE mayreceive, from the base station via PDCCH and/or RRC, an indication of apreamble (e.g., ra-PreambleIndex).

After transmitting a preamble, the UE may start a time window (e.g.,ra-ResponseWindow) to monitor a PDCCH for the RAR. In the event of abeam failure recovery request, the base station may configure the UEwith a separate time window and/or a separate PDCCH in a search spaceindicated by an RRC message (e.g., recoverySearchSpaceId). The UE maymonitor for a PDCCH transmission addressed to a Cell RNTI (C-RNTI) onthe search space. In the contention-free random access procedureillustrated in FIG. 13B, the UE may determine that a random accessprocedure successfully completes after or in response to transmission ofMsg 1 1321 and reception of a corresponding Msg 2 1322. The UE maydetermine that a random access procedure successfully completes, forexample, if a PDCCH transmission is addressed to a C-RNTI. The UE maydetermine that a random access procedure successfully completes, forexample, if the UE receives an RAR comprising a preamble identifiercorresponding to a preamble transmitted by the UE and/or the RARcomprises a MAC sub-PDU with the preamble identifier. The UE maydetermine the response as an indication of an acknowledgement for an SIrequest.

FIG. 13C illustrates another two-step random access procedure. Similarto the random access procedures illustrated in FIGS. 13A and 13B, a basestation may, prior to initiation of the procedure, transmit aconfiguration message 1330 to the UE. The configuration message 1330 maybe analogous in some respects to the configuration message 1310 and/orthe configuration message 1320. The procedure illustrated in FIG. 13Ccomprises transmission of two messages: a Msg A 1331 and a Msg B 1332.

Msg A 1331 may be transmitted in an uplink transmission by the UE. Msg A1331 may comprise one or more transmissions of a preamble 1341 and/orone or more transmissions of a transport block 1342. The transport block1342 may comprise contents that are similar and/or equivalent to thecontents of the Msg 3 1313 illustrated in FIG. 13A. The transport block1342 may comprise UCI (e.g., an SR, a HARQ ACK/NACK, and/or the like).The UE may receive the Msg B 1332 after or in response to transmittingthe Msg A 1331. The Msg B 1332 may comprise contents that are similarand/or equivalent to the contents of the Msg 2 1312 (e.g., an RAR)illustrated in FIGS. 13A and 13B and/or the Msg 4 1314 illustrated inFIG. 13A.

The UE may initiate the two-step random access procedure in FIG. 13C forlicensed spectrum and/or unlicensed spectrum. The UE may determine,based on one or more factors, whether to initiate the two-step randomaccess procedure. The one or more factors may be: a radio accesstechnology in use (e.g., LTE, NR, and/or the like); whether the UE hasvalid TA or not; a cell size; the UE's RRC state; a type of spectrum(e.g., licensed vs. unlicensed); and/or any other suitable factors.

The UE may determine, based on two-step RACH parameters included in theconfiguration message 1330, a radio resource and/or an uplink transmitpower for the preamble 1341 and/or the transport block 1342 included inthe Msg A 1331. The RACH parameters may indicate a modulation and codingschemes (MCS), a time-frequency resource, and/or a power control for thepreamble 1341 and/or the transport block 1342. A time-frequency resourcefor transmission of the preamble 1341 (e.g., a PRACH) and atime-frequency resource for transmission of the transport block 1342(e.g., a PUSCH) may be multiplexed using FDM, TDM, and/or CDM. The RACHparameters may enable the UE to determine a reception timing and adownlink channel for monitoring for and/or receiving Msg B 1332.

The transport block 1342 may comprise data (e.g., delay-sensitive data),an identifier of the UE, security information, and/or device information(e.g., an International Mobile Subscriber Identity (IMSI)). The basestation may transmit the Msg B 1332 as a response to the Msg A 1331. TheMsg B 1332 may comprise at least one of following: a preambleidentifier; a timing advance command; a power control command; an uplinkgrant (e.g., a radio resource assignment and/or an MCS); a UE identifierfor contention resolution; and/or an RNTI (e.g., a C-RNTI or a TC-RNTI).The UE may determine that the two-step random access procedure issuccessfully completed if: a preamble identifier in the Msg B 1332 ismatched to a preamble transmitted by the UE; and/or the identifier ofthe UE in Msg B 1332 is matched to the identifier of the UE in the Msg A1331 (e.g., the transport block 1342).

A UE and a base station may exchange control signaling. The controlsignaling may be referred to as L1/L2 control signaling and mayoriginate from the PHY layer (e.g., layer 1) and/or the MAC layer (e.g.,layer 2). The control signaling may comprise downlink control signalingtransmitted from the base station to the UE and/or uplink controlsignaling transmitted from the UE to the base station.

The downlink control signaling may comprise: a downlink schedulingassignment; an uplink scheduling grant indicating uplink radio resourcesand/or a transport format; a slot format information; a preemptionindication; a power control command; and/or any other suitablesignaling. The UE may receive the downlink control signaling in apayload transmitted by the base station on a physical downlink controlchannel (PDCCH). The payload transmitted on the PDCCH may be referred toas downlink control information (DCI). In some scenarios, the PDCCH maybe a group common PDCCH (GC-PDCCH) that is common to a group of UEs.

A base station may attach one or more cyclic redundancy check (CRC)parity bits to a DCI in order to facilitate detection of transmissionerrors. When the DCI is intended for a UE (or a group of the UEs), thebase station may scramble the CRC parity bits with an identifier of theUE (or an identifier of the group of the UEs). Scrambling the CRC paritybits with the identifier may comprise Modulo-2 addition (or an exclusiveOR operation) of the identifier value and the CRC parity bits. Theidentifier may comprise a 16-bit value of a radio network temporaryidentifier (RNTI).

DCIs may be used for different purposes. A purpose may be indicated bythe type of RNTI used to scramble the CRC parity bits. For example, aDCI having CRC parity bits scrambled with a paging RNTI (P-RNTI) mayindicate paging information and/or a system information changenotification. The P-RNTI may be predefined as “FFFE” in hexadecimal. ADCI having CRC parity bits scrambled with a system information RNTI(SI-RNTI) may indicate a broadcast transmission of the systeminformation. The SI-RNTI may be predefined as “FFFF” in hexadecimal. ADCI having CRC parity bits scrambled with a random access RNTI (RA-RNTI)may indicate a random access response (RAR). A DCI having CRC paritybits scrambled with a cell RNTI (C-RNTI) may indicate a dynamicallyscheduled unicast transmission and/or a triggering of PDCCH-orderedrandom access. A DCI having CRC parity bits scrambled with a temporarycell RNTI (TC-RNTI) may indicate a contention resolution (e.g., a Msg 3analogous to the Msg 3 1313 illustrated in FIG. 13A). Other RNTIsconfigured to the UE by a base station may comprise a ConfiguredScheduling RNTI (CS-RNTI), a Transmit Power Control-PUCCH RNTI(TPC-PUCCH-RNTI), a Transmit Power Control-PUSCH RNTI (TPC-PUSCH-RNTI),a Transmit Power Control-SRS RNTI (TPC-SRS-RNTI), an Interruption RNTI(INT-RNTI), a Slot Format Indication RNTI (SFI-RNTI), a Semi-PersistentCSI RNTI (SP-CSI-RNTI), a Modulation and Coding Scheme Cell RNTI(MCS-C-RNTI), and/or the like.

Depending on the purpose and/or content of a DCI, the base station maytransmit the DCIs with one or more DCI formats. For example, DCI format0_0 may be used for scheduling of PUSCH in a cell. DCI format 0_0 may bea fallback DCI format (e.g., with compact DCI payloads). DCI format 0_1may be used for scheduling of PUSCH in a cell (e.g., with more DCIpayloads than DCI format 0_0). DCI format 1_0 may be used for schedulingof PDSCH in a cell. DCI format 1_0 may be a fallback DCI format (e.g.,with compact DCI payloads). DCI format 1_1 may be used for scheduling ofPDSCH in a cell (e.g., with more DCI payloads than DCI format 1_0). DCIformat 2_0 may be used for providing a slot format indication to a groupof UEs. DCI format 2_1 may be used for notifying a group of UEs of aphysical resource block and/or OFDM symbol where the UE may assume notransmission is intended to the UE. DCI format 2_2 may be used fortransmission of a transmit power control (TPC) command for PUCCH orPUSCH. DCI format 2_3 may be used for transmission of a group of TPCcommands for SRS transmissions by one or more UEs. DCI format(s) for newfunctions may be defined in future releases. DCI formats may havedifferent DCI sizes, or may share the same DCI size.

After scrambling a DCI with a RNTI, the base station may process the DCIwith channel coding (e.g., polar coding), rate matching, scramblingand/or QPSK modulation. A base station may map the coded and modulatedDCI on resource elements used and/or configured for a PDCCH. Based on apayload size of the DCI and/or a coverage of the base station, the basestation may transmit the DCI via a PDCCH occupying a number ofcontiguous control channel elements (CCEs). The number of the contiguousCCEs (referred to as aggregation level) may be 1, 2, 4, 8, 16, and/orany other suitable number. A CCE may comprise a number (e.g., 6) ofresource-element groups (REGs). A REG may comprise a resource block inan OFDM symbol. The mapping of the coded and modulated DCI on theresource elements may be based on mapping of CCEs and REGs (e.g.,CCE-to-REG mapping).

FIG. 14A illustrates an example of CORESET configurations for abandwidth part. The base station may transmit a DCI via a PDCCH on oneor more control resource sets (CORESETs). A CORESET may comprise atime-frequency resource in which the UE tries to decode a DCI using oneor more search spaces. The base station may configure a CORESET in thetime-frequency domain. In the example of FIG. 14A, a first CORESET 1401and a second CORESET 1402 occur at the first symbol in a slot. The firstCORESET 1401 overlaps with the second CORESET 1402 in the frequencydomain. A third CORESET 1403 occurs at a third symbol in the slot. Afourth CORESET 1404 occurs at the seventh symbol in the slot. CORESETsmay have a different number of resource blocks in frequency domain.

FIG. 14B illustrates an example of a CCE-to-REG mapping for DCItransmission on a CORESET and PDCCH processing. The CCE-to-REG mappingmay be an interleaved mapping (e.g., for the purpose of providingfrequency diversity) or a non-interleaved mapping (e.g., for thepurposes of facilitating interference coordination and/orfrequency-selective transmission of control channels). The base stationmay perform different or same CCE-to-REG mapping on different CORESETs.A CORESET may be associated with a CCE-to-REG mapping by RRCconfiguration. A CORESET may be configured with an antenna port quasico-location (QCL) parameter. The antenna port QCL parameter may indicateQCL information of a demodulation reference signal (DMRS) for PDCCHreception in the CORESET.

The base station may transmit, to the UE, RRC messages comprisingconfiguration parameters of one or more CORESETs and one or more searchspace sets. The configuration parameters may indicate an associationbetween a search space set and a CORESET. A search space set maycomprise a set of PDCCH candidates formed by CCEs at a given aggregationlevel. The configuration parameters may indicate: a number of PDCCHcandidates to be monitored per aggregation level; a PDCCH monitoringperiodicity and a PDCCH monitoring pattern; one or more DCI formats tobe monitored by the UE; and/or whether a search space set is a commonsearch space set or a UE-specific search space set. A set of CCEs in thecommon search space set may be predefined and known to the UE. A set ofCCEs in the UE-specific search space set may be configured based on theUE's identity (e.g., C-RNTI).

As shown in FIG. 14B, the UE may determine a time-frequency resource fora CORESET based on RRC messages. The UE may determine a CCE-to-REGmapping (e.g., interleaved or non-interleaved, and/or mappingparameters) for the CORESET based on configuration parameters of theCORESET. The UE may determine a number (e.g., at most 10) of searchspace sets configured on the CORESET based on the RRC messages. The UEmay monitor a set of PDCCH candidates according to configurationparameters of a search space set. The UE may monitor a set of PDCCHcandidates in one or more CORESETs for detecting one or more DCIs.Monitoring may comprise decoding one or more PDCCH candidates of the setof the PDCCH candidates according to the monitored DCI formats.Monitoring may comprise decoding a DCI content of one or more PDCCHcandidates with possible (or configured) PDCCH locations, possible (orconfigured) PDCCH formats (e.g., number of CCEs, number of PDCCHcandidates in common search spaces, and/or number of PDCCH candidates inthe UE-specific search spaces) and possible (or configured) DCI formats.The decoding may be referred to as blind decoding. The UE may determinea DCI as valid for the UE, in response to CRC checking (e.g., scrambledbits for CRC parity bits of the DCI matching a RNTI value). The UE mayprocess information contained in the DCI (e.g., a scheduling assignment,an uplink grant, power control, a slot format indication, a downlinkpreemption, and/or the like).

The UE may transmit uplink control signaling (e.g., uplink controlinformation (UCI)) to a base station. The uplink control signaling maycomprise hybrid automatic repeat request (HARQ) acknowledgements forreceived DL-SCH transport blocks. The UE may transmit the HARQacknowledgements after receiving a DL-SCH transport block. Uplinkcontrol signaling may comprise channel state information (CSI)indicating channel quality of a physical downlink channel. The UE maytransmit the CSI to the base station. The base station, based on thereceived CSI, may determine transmission format parameters (e.g.,comprising multi-antenna and beamforming schemes) for a downlinktransmission. Uplink control signaling may comprise scheduling requests(SR). The UE may transmit an SR indicating that uplink data is availablefor transmission to the base station. The UE may transmit a UCI (e.g.,HARQ acknowledgements (HARQ-ACK), CSI report, SR, and the like) via aphysical uplink control channel (PUCCH) or a physical uplink sharedchannel (PUSCH). The UE may transmit the uplink control signaling via aPUCCH using one of several PUCCH formats.

There may be five PUCCH formats and the UE may determine a PUCCH formatbased on a size of the UCI (e.g., a number of uplink symbols of UCItransmission and a number of UCI bits). PUCCH format 0 may have a lengthof one or two OFDM symbols and may include two or fewer bits. The UE maytransmit UCI in a PUCCH resource using PUCCH format 0 if thetransmission is over one or two symbols and the number of HARQ-ACKinformation bits with positive or negative SR (HARQ-ACK/SR bits) is oneor two. PUCCH format 1 may occupy a number between four and fourteenOFDM symbols and may include two or fewer bits. The UE may use PUCCHformat 1 if the transmission is four or more symbols and the number ofHARQ-ACK/SR bits is one or two. PUCCH format 2 may occupy one or twoOFDM symbols and may include more than two bits. The UE may use PUCCHformat 2 if the transmission is over one or two symbols and the numberof UCI bits is two or more. PUCCH format 3 may occupy a number betweenfour and fourteen OFDM symbols and may include more than two bits. TheUE may use PUCCH format 3 if the transmission is four or more symbols,the number of UCI bits is two or more and PUCCH resource does notinclude an orthogonal cover code. PUCCH format 4 may occupy a numberbetween four and fourteen OFDM symbols and may include more than twobits. The UE may use PUCCH format 4 if the transmission is four or moresymbols, the number of UCI bits is two or more and the PUCCH resourceincludes an orthogonal cover code.

The base station may transmit configuration parameters to the UE for aplurality of PUCCH resource sets using, for example, an RRC message. Theplurality of PUCCH resource sets (e.g., up to four sets) may beconfigured on an uplink BWP of a cell. A PUCCH resource set may beconfigured with a PUCCH resource set index, a plurality of PUCCHresources with a PUCCH resource being identified by a PUCCH resourceidentifier (e.g., pucch-ResourceId), and/or a number (e.g. a maximumnumber) of UCI information bits the UE may transmit using one of theplurality of PUCCH resources in the PUCCH resource set. When configuredwith a plurality of PUCCH resource sets, the UE may select one of theplurality of PUCCH resource sets based on a total bit length of the UCIinformation bits (e.g., HARQ-ACK, SR, and/or CSI). If the total bitlength of UCI information bits is two or fewer, the UE may select afirst PUCCH resource set having a PUCCH resource set index equal to “0”.If the total bit length of UCI information bits is greater than two andless than or equal to a first configured value, the UE may select asecond PUCCH resource set having a PUCCH resource set index equal to“1”. If the total bit length of UCI information bits is greater than thefirst configured value and less than or equal to a second configuredvalue, the UE may select a third PUCCH resource set having a PUCCHresource set index equal to “2”. If the total bit length of UCIinformation bits is greater than the second configured value and lessthan or equal to a third value (e.g., 1406), the UE may select a fourthPUCCH resource set having a PUCCH resource set index equal to “3”.

After determining a PUCCH resource set from a plurality of PUCCHresource sets, the UE may determine a PUCCH resource from the PUCCHresource set for UCI (HARQ-ACK, CSI, and/or SR) transmission. The UE maydetermine the PUCCH resource based on a PUCCH resource indicator in aDCI (e.g., with a DCI format 1_0 or DCI for 1_1) received on a PDCCH. Athree-bit PUCCH resource indicator in the DCI may indicate one of eightPUCCH resources in the PUCCH resource set. Based on the PUCCH resourceindicator, the UE may transmit the UCI (HARQ-ACK, CSI and/or SR) using aPUCCH resource indicated by the PUCCH resource indicator in the DCI.

FIG. 15 illustrates an example of a wireless device 1502 incommunication with a base station 1504 in accordance with embodiments ofthe present disclosure. The wireless device 1502 and base station 1504may be part of a mobile communication network, such as the mobilecommunication network 100 illustrated in FIG. 1A, the mobilecommunication network 150 illustrated in FIG. 1B, or any othercommunication network. Only one wireless device 1502 and one basestation 1504 are illustrated in FIG. 15, but it will be understood thata mobile communication network may include more than one UE and/or morethan one base station, with the same or similar configuration as thoseshown in FIG. 15.

The base station 1504 may connect the wireless device 1502 to a corenetwork (not shown) through radio communications over the air interface(or radio interface) 1506. The communication direction from the basestation 1504 to the wireless device 1502 over the air interface 1506 isknown as the downlink, and the communication direction from the wirelessdevice 1502 to the base station 1504 over the air interface is known asthe uplink. Downlink transmissions may be separated from uplinktransmissions using FDD, TDD, and/or some combination of the twoduplexing techniques.

In the downlink, data to be sent to the wireless device 1502 from thebase station 1504 may be provided to the processing system 1508 of thebase station 1504. The data may be provided to the processing system1508 by, for example, a core network. In the uplink, data to be sent tothe base station 1504 from the wireless device 1502 may be provided tothe processing system 1518 of the wireless device 1502. The processingsystem 1508 and the processing system 1518 may implement layer 3 andlayer 2 OSI functionality to process the data for transmission. Layer 2may include an SDAP layer, a PDCP layer, an RLC layer, and a MAC layer,for example, with respect to FIG. 2A, FIG. 2B, FIG. 3, and FIG. 4A.Layer 3 may include an RRC layer as with respect to FIG. 2B.

After being processed by processing system 1508, the data to be sent tothe wireless device 1502 may be provided to a transmission processingsystem 1510 of base station 1504. Similarly, after being processed bythe processing system 1518, the data to be sent to base station 1504 maybe provided to a transmission processing system 1520 of the wirelessdevice 1502. The transmission processing system 1510 and thetransmission processing system 1520 may implement layer 1 OSIfunctionality. Layer 1 may include a PHY layer with respect to FIG. 2A,FIG. 2B, FIG. 3, and FIG. 4A. For transmit processing, the PHY layer mayperform, for example, forward error correction coding of transportchannels, interleaving, rate matching, mapping of transport channels tophysical channels, modulation of physical channel, multiple-inputmultiple-output (MIMO) or multi-antenna processing, and/or the like.

At the base station 1504, a reception processing system 1512 may receivethe uplink transmission from the wireless device 1502. At the wirelessdevice 1502, a reception processing system 1522 may receive the downlinktransmission from base station 1504. The reception processing system1512 and the reception processing system 1522 may implement layer 1 OSIfunctionality. Layer 1 may include a PHY layer with respect to FIG. 2A,FIG. 2B, FIG. 3, and FIG. 4A. For receive processing, the PHY layer mayperform, for example, error detection, forward error correctiondecoding, deinterleaving, demapping of transport channels to physicalchannels, demodulation of physical channels, MIMO or multi-antennaprocessing, and/or the like.

As shown in FIG. 15, a wireless device 1502 and the base station 1504may include multiple antennas. The multiple antennas may be used toperform one or more MIMO or multi-antenna techniques, such as spatialmultiplexing (e.g., single-user MIMO or multi-user MIMO),transmit/receive diversity, and/or beamforming. In other examples, thewireless device 1502 and/or the base station 1504 may have a singleantenna.

The processing system 1508 and the processing system 1518 may beassociated with a memory 1514 and a memory 1524, respectively. Memory1514 and memory 1524 (e.g., one or more non-transitory computer readablemediums) may store computer program instructions or code that may beexecuted by the processing system 1508 and/or the processing system 1518to carry out one or more of the functionalities discussed in the presentapplication. Although not shown in FIG. 15, the transmission processingsystem 1510, the transmission processing system 1520, the receptionprocessing system 1512, and/or the reception processing system 1522 maybe coupled to a memory (e.g., one or more non-transitory computerreadable mediums) storing computer program instructions or code that maybe executed to carry out one or more of their respectivefunctionalities.

The processing system 1508 and/or the processing system 1518 maycomprise one or more controllers and/or one or more processors. The oneor more controllers and/or one or more processors may comprise, forexample, a general-purpose processor, a digital signal processor (DSP),a microcontroller, an application specific integrated circuit (ASIC), afield programmable gate array (FPGA) and/or other programmable logicdevice, discrete gate and/or transistor logic, discrete hardwarecomponents, an on-board unit, or any combination thereof. The processingsystem 1508 and/or the processing system 1518 may perform at least oneof signal coding/processing, data processing, power control,input/output processing, and/or any other functionality that may enablethe wireless device 1502 and the base station 1504 to operate in awireless environment.

The processing system 1508 and/or the processing system 1518 may beconnected to one or more peripherals 1516 and one or more peripherals1526, respectively. The one or more peripherals 1516 and the one or moreperipherals 1526 may include software and/or hardware that providefeatures and/or functionalities, for example, a speaker, a microphone, akeypad, a display, a touchpad, a power source, a satellite transceiver,a universal serial bus (USB) port, a hands-free headset, a frequencymodulated (FM) radio unit, a media player, an Internet browser, anelectronic control unit (e.g., for a motor vehicle), and/or one or moresensors (e.g., an accelerometer, a gyroscope, a temperature sensor, aradar sensor, a lidar sensor, an ultrasonic sensor, a light sensor, acamera, and/or the like). The processing system 1508 and/or theprocessing system 1518 may receive user input data from and/or provideuser output data to the one or more peripherals 1516 and/or the one ormore peripherals 1526. The processing system 1518 in the wireless device1502 may receive power from a power source and/or may be configured todistribute the power to the other components in the wireless device1502. The power source may comprise one or more sources of power, forexample, a battery, a solar cell, a fuel cell, or any combinationthereof. The processing system 1508 and/or the processing system 1518may be connected to a GPS chipset 1517 and a GPS chipset 1527,respectively. The GPS chipset 1517 and the GPS chipset 1527 may beconfigured to provide geographic location information of the wirelessdevice 1502 and the base station 1504, respectively.

FIG. 16A illustrates an example structure for uplink transmission. Abaseband signal representing a physical uplink shared channel mayperform one or more functions. The one or more functions may comprise atleast one of: scrambling; modulation of scrambled bits to generatecomplex-valued symbols; mapping of the complex-valued modulation symbolsonto one or several transmission layers; transform precoding to generatecomplex-valued symbols; precoding of the complex-valued symbols; mappingof precoded complex-valued symbols to resource elements; generation ofcomplex-valued time-domain Single Carrier-Frequency Division MultipleAccess (SC-FDMA) or CP-OFDM signal for an antenna port; and/or the like.In an example, when transform precoding is enabled, a SC-FDMA signal foruplink transmission may be generated. In an example, when transformprecoding is not enabled, an CP-OFDM signal for uplink transmission maybe generated by FIG. 16A. These functions are illustrated as examplesand it is anticipated that other mechanisms may be implemented invarious embodiments.

FIG. 16B illustrates an example structure for modulation andup-conversion of a baseband signal to a carrier frequency. The basebandsignal may be a complex-valued SC-FDMA or CP-OFDM baseband signal for anantenna port and/or a complex-valued Physical Random Access Channel(PRACH) baseband signal. Filtering may be employed prior totransmission.

FIG. 16C illustrates an example structure for downlink transmissions. Abaseband signal representing a physical downlink channel may perform oneor more functions. The one or more functions may comprise: scrambling ofcoded bits in a codeword to be transmitted on a physical channel;modulation of scrambled bits to generate complex-valued modulationsymbols; mapping of the complex-valued modulation symbols onto one orseveral transmission layers; precoding of the complex-valued modulationsymbols on a layer for transmission on the antenna ports; mapping ofcomplex-valued modulation symbols for an antenna port to resourceelements; generation of complex-valued time-domain OFDM signal for anantenna port; and/or the like. These functions are illustrated asexamples and it is anticipated that other mechanisms may be implementedin various embodiments.

FIG. 16D illustrates another example structure for modulation andup-conversion of a baseband signal to a carrier frequency. The basebandsignal may be a complex-valued OFDM baseband signal for an antenna port.Filtering may be employed prior to transmission.

A wireless device may receive from a base station one or more messages(e.g. RRC messages) comprising configuration parameters of a pluralityof cells (e.g. primary cell, secondary cell). The wireless device maycommunicate with at least one base station (e.g. two or more basestations in dual-connectivity) via the plurality of cells. The one ormore messages (e.g. as a part of the configuration parameters) maycomprise parameters of physical, MAC, RLC, PCDP, SDAP, RRC layers forconfiguring the wireless device. For example, the configurationparameters may comprise parameters for configuring physical and MAClayer channels, bearers, etc. For example, the configuration parametersmay comprise parameters indicating values of timers for physical, MAC,RLC, PCDP, SDAP, RRC layers, and/or communication channels.

A timer may begin running once it is started and continue running untilit is stopped or until it expires. A timer may be started if it is notrunning or restarted if it is running. A timer may be associated with avalue (e.g. the timer may be started or restarted from a value or may bestarted from zero and expire once it reaches the value). The duration ofa timer may not be updated until the timer is stopped or expires (e.g.,due to BWP switching). A timer may be used to measure a timeperiod/window for a process. When the specification refers to animplementation and procedure related to one or more timers, it will beunderstood that there are multiple ways to implement the one or moretimers. For example, it will be understood that one or more of themultiple ways to implement a timer may be used to measure a timeperiod/window for the procedure. For example, a random access responsewindow timer may be used for measuring a window of time for receiving arandom access response. In an example, instead of starting and expiry ofa random access response window timer, the time difference between twotime stamps may be used. When a timer is restarted, a process formeasurement of time window may be restarted. Other exampleimplementations may be provided to restart a measurement of a timewindow.

In an example, D2D (device to device) communication literally meanscommunication between an electronic device and an electronic device.According to a D2D communication scheme or a UE-to-UE communicationscheme, data may be exchanged between UEs without passing through a basestation. A link directly established between devices may be referred toas a D2D link or a sidelink. The D2D communication may have merits inthat latency is reduced compared to a legacy base station-centeredcommunication scheme and a less radio resource is required, and thelike. In this case, although a UE corresponds to a terminal of a user,if such a network device as an eNB or a gNB transmits and receives asignal according to a communication scheme between UEs, the networkdevice may be considered as a sort of UEs.

FIG. 17 shows deployment examples of types of UE performing D2Dcommunication and cell coverage. Referring to FIG. 17A, types of UE Aand B may be placed outside cell coverage. Referring to FIG. 17B, UE Amay be placed within cell coverage, and UE B may be placed outside cellcoverage. Referring to FIG. 17C, types of UE A and B may be placedwithin single cell coverage. Referring to FIG. 17D, UE A may be placedwithin coverage of a first cell, and UE B may be placed within coverageof a second cell.

In an example, a D2D transmission signal transmitted through a sidelinkmay be divided into a discovery use and a communication use. A discoverysignal corresponds to a signal used by a UE to determine a plurality ofUEs adjacent to the UE. As an example of a sidelink channel fortransmitting and receiving the discovery signal, there is a sidelinkdiscovery channel (PSDCH: Physical Sidelink Discovery Channel). Acommunication signal corresponds to a signal for transmitting generaldata (e.g., voice, image, video, safety information, etc.) to betransmitted by a UE. As an example of a sidelink channel fortransmitting and receiving the communication signal, there are aphysical sidelink broadcast channel (PSBCH), a physical sidelink sharedchannel (PSSCH), a physical sidelink control channel (PSCCH), and thelike.

FIG. 18 shows an example of a UE A, a UE B and a radio resources used bythe UE A and the UE B performing D2D communication. In FIG. 18A, a UEcorresponds to a terminal or such a network device as a base stationtransmitting and receiving a signal according to a D2D communicationscheme. A UE selects a resource unit corresponding to a specificresource from a resource pool corresponding to a set of resources andthe UE transmits a D2D signal using the selected resource unit. The UE Bcorresponding to a reception UE receives a configuration of a resourcepool in which the UE A is able to transmit a signal and the UE B is ableto detect a signal of the UE A in the resource pool. In this case, ifthe UE A is located at the inside of network coverage of a base station,the base station may inform the UE A of the resource pool. If the UE Ais located at the outside of network coverage of the base station, theresource pool may be informed by a different UE or may be determined bya preconfigured resource pool. In general, a resource pool includes aplurality of resource units. One resource unit may be comprised of agroup of resource blocks. A UE selects one or more resource units from aplurality of the resource units and may be able to use the selectedresource unit(s) for D2D signal transmission. FIG. 18B shows an exampleof configuring a resource unit. Referring to FIG. 18B, the entirefrequency resources are divided into the Nf number of resource units pera unit time resource (e.g. slot or a group of slots). A resource poolmay be repeated with a period of k unit time resources and a resourcepool may be configured within a bandwidth part for D2D or sidelinkcommunication. Specifically, as shown in FIG. 18, one resource unit mayperiodically and repeatedly appear, or, an index of a physical resourceunit to which a logical resource unit is mapped may change with apredetermined pattern according to time to obtain a diversity gain intime domain and/or frequency domain. In this resource unit structure, aresource pool may correspond to a set of resource units capable of beingused by a UE intending to transmit or receive a D2D signal.

In an example, a resource pool may be classified into various types. Aresource pool may be classified according to contents of a D2D signaltransmitted via each resource pool. For example, the contents of the D2Dsignal may be classified into various signals and a separate resourcepool may be configured according to each of the contents. The contentsof the D2D signal may include a D2D control channel, a D2D data channel,and/or a discovery channel. The D2D control channel may correspond to asignal including information on a resource position of a D2D datachannel, information on MCS necessary for modulating and demodulating adata channel, information on a MIMO transmission scheme, information onpacket priority, information on target coverage, information on QoSrequirement or the like. The D2D control channel may be transmitted onan identical resource unit in a manner of being multiplexed with D2Ddata channel. In this case, a D2D control and data channel resource poolmay correspond to a pool of resources that D2D control and D2D data aretransmitted in a manner of being multiplexed. As shown in FIG. 22, theD2D control channel may also be referred to as a PSCCH (physicalsidelink control channel). The D2D data channel (or, PSSCH (physicalsidelink shared channel)) corresponds to a resource pool used by atransmission UE to transmit user data. If a D2D control and a D2D dataare transmitted in a manner of being multiplexed in an identicalresource unit, D2D data channel except D2D control information may betransmitted only in a resource pool for the D2D data channel. In otherword, resource elements (REs), which are used to transmit D2D controlinformation in a specific resource unit of a D2D control resource pool,may also be used for transmitting D2D data in a D2D data channelresource pool. The discovery channel may correspond to a resource poolfor a message that enables a neighboring UE to discover transmission UEtransmitting information such as ID of the UE, and the like.

In an example, a resource pool may be classified to support differentQoS level or different service. For example, the priority level for eachresource pool may be configured by a base station, or the service to besupported for each resource pool may be configured differently.Alternatively, a specific resource pool may be configured to use only aspecific unicast or groupcast UEs. Although contents of D2D signal areidentical to each other, it may use a different resource pool accordingto a transmission/reception attribute of the D2D signal. For example, incase of the same D2D data channel or the same discovery message, the D2Ddata channel or the discovery signal may be classified into a differentresource pool according to a transmission timing determination scheme(e.g., whether a D2D signal is transmitted at the time of receiving asynchronization reference signal or the timing to which a prescribedtiming advance is added) of a D2D signal, a resource allocation scheme(e.g., whether a transmission resource of an individual signal isdesignated by a base station or an individual transmission UE selects anindividual signal transmission resource from a pool), a signal format(e.g., number of symbols occupied by a D2D signal in a subframe, numberof subframes used for transmitting a D2D signal), signal strength from abase station, strength of transmit power of a D2D UE, and the like. Forclarity, a method for a base station to directly designate atransmission resource of a D2D transmission UE is referred to as a Mode1 (e.g., model operation). In Mode 1, a base station such as eNB or gNBmay transmit DCI to schedule D2D signal transmission. If a transmissionresource region (or resource pool) is (pre)configured or a base stationdesignates the transmission resource region or resource pool and a UEdirectly selects a transmission resource from the transmission resourceregion (or resource pool), it is referred to as a Mode 2 (e.g., mode2operation). In case of performing D2D discovery, if a base stationdirectly indicates a transmission resource, it is referred to as a Type2. If a UE directly selects a transmission resource from a predeterminedresource pool or a resource pool indicated by the base station, it isreferred to as a Type 1.

In an example, for D2D communication, it may be necessary to obtain timesynchronization and frequency synchronization between two UEs. If thetwo UEs belong to the coverage of a cell, the two UEs may besynchronized by a PSS/SSS, or the like transmitted by the base stationand the time/frequency synchronization may be maintained between the twoUEs in a level that the two UEs are able to directly transmit andreceive a signal. Alternatively, a UE may transmit synchronizationsignal and another UE may be synchronized to the synchronization signaltransmitted by the UE. This synchronization signal transmitted by a UEmay be referred to as a sidelink synchronization signal (SLSS). SLSS maycomprise sidelink primary synchronization signal (S-PSS) and sidelinksecondary synchronization signal (S-SSS). SLSS may be transmitted withphysical sidelink broadcast channel (PSBCH) to convey some basic orinitial system information. Additionally, a UE may synchronize or derivea timing of transmission time intervals (e.g., frames, subframes, slots,and/or the like) using global navigation satellite system (GNSS) timing.S-PSS, S-SSS and PSBCH may be structured in a block format (sidelinksynchronization signal block (S-SSB)) which may support periodictransmission. The S-SSB may have the same numerology (i.e. SCS and CPlength) as sidelink data channel and sidelink control channel in acarrier, transmission bandwidth may be within the (pre-)configuredsidelink BWP, and its frequency location may be (pre-)configured, asshown in FIG. 23 and/or FIG. 24. This may lead to no need for the UE toperform hypothesis detection in frequency to find S-SSB in a carrier.Sidelink synchronization sources may be GNSS, gNB, eNB, or NR UE. Eachsidelink synchronization source may be associated with a synchronizationpriority level in which the priority order may be (pre)configured.

In an example, as shown in FIG. 19, a D2D resource pool may be to dividea bandwidth into multiple subchannels, wherein each transmitter of anumber of neighboring transmitters may select one or more subchannels totransmit a signal. Subchannel selection may be based on received energymeasurements and/or control channel decoding. As an example, a UE mayidentify which subchannel is going to be used by other UE based oncontrol channel decoding as well as an energy measurement for eachsubchannel. Here, a limit on system performance may be imposed byin-band emissions. An in-band emission (IBE) is interference caused byone transmitter transmitting on one subchannel and imposed on anothertransmitter transmitting to a receiver on another subchannel. FIG. 19 isa diagram illustrating an in-band emissions model. Referring to FIG. 19,the plot of the in-band emissions model shows that nearby subchannels aswell as other subchannels (e.g., I/Q or image subchannels) experiencemore interference.

In an example, when the D2D UE operates in the cellular network, thepower radiated by the D2D UE may cause serious interference to thecellular communication. In particular, when a D2D UE uses only somefrequency resources in a particular slot or subframe, the inbandemission of the power radiated by the D2D UE may cause seriousinterference to the frequency resources used by the cellular UE. Toprevent this problem, the D2D UE may perform a cellular pathloss-basedpower control. At this time, the parameters (e. g. P0 or alpha) used forpower control may be configured by the base station.

In an example, in a D2D communication, the transmission UE maycorrespond to a half-duplex UE which is unable to perform reception atthe time of performing transmission. In particular, the transmission UEmay fail to receive the transmission of the different UE due to thehalf-duplex problem. To mitigate half duplex problem, different D2D UEsperforming communication need to transmit signals at least one or moredifferent time resources.

In an example, D2D operation may have various advantages in that it iscommunication between devices in proximity. For example, D2D UE has ahigh transfer rate and a low delay and may perform data communication.Furthermore, in D2D operation, traffic concentrated on a base stationmay be distributed. If D2D UE plays the role of a relay, it may alsoplay the role of extending coverage of a base station.

In an example, as shown in FIG. 20, the D2D communication may beexpanded and/or applied to signal transmission and/or reception betweenvehicles. Vehicle-related communication may be referred to asvehicle-to-everything (V2X) communication. In V2X, the term ‘X’ refersto a pedestrian (communication between a vehicle and a device carried byan individual (e.g.: handheld terminal carried by a pedestrian, cyclist,driver or passenger), in this case, V2X may be indicated V2P), a vehicle(communication between vehicles) (V2V), an infrastructure/network(communication between a vehicle and a roadside unit (RSU)/network(e.g., RSU is a transportation infrastructure entity (e.g., an entitytransmitting speed notifications) implemented in a base station or astationary UE)) (V2I/N), and so on. For V2X communication, a vehicle, anRSU and a handheld device may be equipped with a transceiver. FIG. 19illustrates a diagram of V2X communication.

In an example, V2X communication may be used to indicate warnings forvarious events such as safety and the like. For example, information onan event occurring on a vehicle or road may be notified to anothervehicle or pedestrians through V2X communication. For example,information on a warning of a traffic accident, a change of a roadsituation, or an accident occurrence may be forwarded to another vehicleor pedestrian. For example, a pedestrian, who is adjacent to or crossinga road, may be informed of information on vehicle approach.

In an example, in V2X communication, one challenge may be to avoidcollisions and guarantee a minimum communication quality even in denseUE scenario. Wireless congestion control may represent a family ofmechanisms to mitigate such collisions by adjusting communicationparameter to control the congestion level on the vehicular wirelesschannel and guarantee reliable V2X communications. In exampletechnologies, a wireless device may measure the following two metrics tocharacterize the channel state and allow the wireless device to takenecessary actions: 1) channel busy radio (CBR): defined as the portion(or number) of subchannels in the resource pool whose RSSI measuredexceeds a pre-configured threshold, wherein the total frequencyresources may be divided into a given number of subchannels. Such metricmay be sensed over the last 100 subframes (where the definition of“subframe” in LTE may be used). It may provide an estimation on thetotal state of the channel. 2) Channel occupancy ratio (CR): calculatedat subframe n, it is defined as the total number of subchannels used forits transmissions in subframes [n−a, n−1] and granted in subframes [n,n+b] divided by the total number of subchannels within [n−a, n+b]. a andb are determined by the station with the limitation of a+b+1=1000,a≥500. The CR may provide an indication on the channel utilization bythe transmitter itself. For each interval of CBR values, a CR limit maybe defined as a footprint that the transmitter should not exceed. ThisCR limit may be configured by a base station per a CBR range and packetpriority. For example, if a high CBR is observed, a low CR limit may beconfigured, and a low CR limit may be configured for a low packetpriority. When the station decides to transmit a packet, it maps its CBRvalue to the correct interval to get the corresponding CR limit value.If its CR is higher than the CR limit, the wireless device may have todecrease its CR below that limit. To reduce the CR, it may be up to eachimplementation to decide which technique(s) to use. In an example, thefollowing options to accommodate CR limit may be taken into account: 1)drop packet retransmission: if the retransmission feature is enabled,the station may disable it. 2) drop packet transmission: the stationsimply drops the packet transmission (including the retransmission ifenabled). This is one of the simplest techniques. 3) adapt the MCS: thewireless device may reduce its CR by augmenting the MCS index used. Thismay reduce the number of subchannels used for the transmission. However,increasing the MCS reduces the robustness of the message, and thusreduces the range of the message. 4) adapt transmission power: thestation may reduce its transmission power. Consequently, the overall CBRin the area may be reduced, and the value of CR limit might beincreased.

In an example, in open loop MIMO, preferred PMI may not be indicated byreceiver. In this case, a cyclic delay diversity (CDD) may be consideredto enhance the decoding performance. CDD may involve transmitting thesame set of a different delay on each antenna. The delay may be appliedbefore the cyclic prefix is added, thereby guaranteeing that the delaymay be cyclic over the FFT size. This gives CDD its name. Adding a timedelay may be identical to applying a phase shift in the frequencydomain. As the same time delay is applied to all subcarriers, the phaseshift will increase linearly across the subcarriers with increasingsubcarrier frequency. Therefore, each subcarrier may experience adifferent beamforming pattern as the non-delayed subcarrier from oneantenna interferes constructively od destructively with the delayedversion from another antenna. The diversity effect of CDD thereforearises from the fact that different subcarriers will pick out differentspatial paths in the propagation channel, thus increasing thefrequency-selectivity of the channel. The channel coding, which isapplied to a whole transport block across the subcarriers, ensures thatthe whole transport block benefits from the diversity of spatial paths.The general principle of the CDD technique is illustrated in FIG. 21.The fact that the delay is added before the CP means that any delayvalue may be used without increasing the overall delay spread of thechannel. If the delay value is greater than CP length, the additional RSneeds to be transmitted to estimate channel of delayed versiondifferently. To distinguish between the two cases, a scheme that uses adelay shorter than the CP length is a small delay CDD (SD-CDD), andanother scheme that requires an additional RS with a delay larger thanthe CP length is called a large delay CDD (LD-CDD).

In existing sidelink technologies, a base station may configure sidelinkbearers of a wireless device to use the mode 1 operation to determineradio resources for transmission of corresponding transport blocks. Whenradio resources of the base station are overloaded, the mode 1 operationfor the sidelink bearers of the wireless device may increase trafficload on the radio resource of the base station. To reconfigure thesidelink bearers using the mode 1 operation to use mode 2 operation, inexisting technologies, a base station and a wireless device may releasethe sidelink bearer and the wireless device may perform a bearerestablishment procedure with a receiver device to configure the sidelinkbearer to use the mode 2 operation for resource allocation. The existingmechanism to configure a sidelink resource allocation mode may increaseinefficient signaling and delay to adapt to the latest radio resourcestatus of a wireless network. The existing technologies may increaseinefficient sidelink resource utilization and signaling complexity.There is a need to reduce inefficient signaling to change a resourceallocation mode for sidelink bearers.

Example embodiments support a wireless device to change/reconfigure aresource allocation mode of a sidelink bearer from the mode 1 operationto the mode 2 operation depending on a radio resource status withoutreleasing the sidelink bearer configured to use the mode 1 operation. Inan implementation of example embodiments, a base station may send, to awireless device, a reconfiguration indication indicating that a sidelinkbearer using the mode 1 operation to use the mode 2 operation forresource allocation. In an example, a base station may send, to a targetbase station for a handover or a secondary node addition of a wirelessdevice, information that a sidelink bearer of the wireless device isconfigured to use of the mode 1 operation. The target base station maysend, for the wireless device, a handover command indicating areconfiguration of the sidelink bearer to use the mode 2 operation,based on a radio resource status of the target base station and/or atarget cell. Example embodiments may decrease signaling complexity toconfigure a proper sidelink resource allocation mode depending on aradio resource status.

Example embodiments support a base station to determine a sidelinkresource allocation mode for a sidelink bearer based on QoS measurementresults of the sidelink bearer. A wireless device may send QoSmeasurement results of sidelink bearers to a base station. The basestation may send, to the wireless device, bearer configurationparameters of the sidelink bearers based on the QoS measurement resultsof sidelink bearers. Example embodiments may increase sidelink servicereliability and efficiency of radio resource utilization.

In existing sidelink technologies, a wireless device may configuresidelink bearers as a mode 2 bearer (e.g., bearer that uses the mode 2operation to select radio resources for transmission of correspondingtransport blocks) or a mode 1 operation. To change/configure thesidelink bearers using the mode 2 operation to use mode 1 operation orvice versa, in existing technologies, a base station needs a bearerconfiguration request from the wireless device. The existing resourceallocation mode change/configuration may increase delay to adapt to thelatest network status or radio resource status of a base station as awireless device has limited information of the network status or theradio resource status. The existing technologies may increaseinefficient sidelink resource utilization.

Example embodiments support a base station to configure/change thesidelink resource allocation mode depending on a network status or aradio resource status without a request from a wireless device. In animplementation of example embodiments, a base station stores/keepsinformation of a resource allocation mode (e.g., mode 1 operation ormode 2 operation) of sidelink bearers of a wireless device andchanges/configure the resource allocation mode based on the networkstatus and/or the radio resource status. In an example, the base stationsends the information of the resource allocation mode of the sidelinkbearers to a target base station of a handover or a secondary nodeaddition (e.g., dual/multi connectivity) for the wireless device. Thetarget base station may determine/change/configure the resourceallocation mode based on the network status and/or the radio resourcestatus of the target base station and/or a target cell. Exampleembodiments may increase efficient sidelink resource utilization byconfiguring a proper sidelink resource allocation mode depending on anetwork status or a radio resource status.

In an example, as shown in FIG. 25, a first wireless device (e.g., UE1,a first vehicle, a first sidelink wireless device, a firstdevice-to-device communication wireless device, etc.) may communicatewith a second wireless device (e.g., UE2, a second vehicle, a secondsidelink wireless device, a second device-to-device communicationwireless device, etc.). The first wireless device may have a PC5-RRCconnection with the second wireless device. The first wireless devicemay have a direct connection (e.g., sidelink direct communicationconnection), a PC5 connection, a sidelink connection, and/or the likewith the second wireless device. In an example, the second wirelessdevice may communicate with a second base station.

In an example, the first wireless device may communicate with a thirdwireless device (e.g., UE3, a third vehicle, a third sidelink wirelessdevice, a third device-to-device communication wireless device, etc.).The first wireless device may be connected with the third wirelessdevice via at least one of: a second PC5-RRC connection; a second directconnection (e.g., sidelink direct communication connection), a secondPC5 connection, a second sidelink connection, and/or the like. The firstwireless device may multicast/broadcast/transmit transport blocks to thesecond wireless device and/or the third wireless device. The firstwireless device, the second wireless device, and/or the third wirelessdevice may belong to the same sidelink multicast group.

In an example, as shown in FIG. 25, the first wireless device may havean RRC connection with a first base station (e.g., gNB1, gNB, eNB, RNC,IAB-node, IAB-donor, gNB-DU, gNB-CU, access node, etc.). The first basestation may be a serving base station of the first wireless device. Thefirst base station may serve the first wireless device via at least oneserving cell (e.g., comprising at least one of: a first primary cell,one or more first secondary cells, etc.) comprising a first cell. Thefirst base station may be a camp-on base station of the first wirelessdevice (e.g., if the first wireless device is in an RRC inactive stateand/or an RRC idle state). The first wireless device may communicatewith the second wireless device based on the model operation and/or themode2 operation (e.g., model sidelink resource selection and/or mode2sidelink resource selection). In an example, the first base station maycomprise a cell that is a serving cell and/or a camp-on cell of thesecond wireless device. In an example, the first cell may be a servingcell and/or a camp-on cell of the second wireless device.

In an example, as shown in FIG. 25, the second wireless device may beserved by a second base station (e.g., gNB2, gNB, eNB, RNC, IAB-node,IAB-donor, gNB-DU, gNB-CU, access node, etc.). The second wirelessdevice may have an RRC connection with the second base station. Thefirst wireless device may make an RRC connection with the second basestation. In an example, a second cell of the second base station may beat least one of a handover target cell, a secondary cell (e.g., primarysecondary cell or a cell of secondary cell group), and/or a serving cellof the first wireless device. In an example, the second wireless devicemay be in an RRC idle state or an RRC inactive state at a cell of thesecond base station (e.g., camping on a cell of the second basestation). In an example, the first base station may have a directconnection (e.g., Xn interface, X2 interface, etc.) and/or an indirectconnection (e.g., via one or more N2/S1 interfaces, one or moreAMFs/MMEs, etc.) with the second base station.

In an example, as shown in FIG. 25 and/or FIG. 26, a first wirelessdevice may establish a first sidelink bearer between the first wirelessdevice and a second wireless device. The first sidelink bearer may beconfigured to use radio resources based on a mode 2 operation. The firstwireless device may send, to a first base station, first bearerconfiguration parameters of the first sidelink bearer. In an example,the first base station may determine, based on the first bearerconfiguration parameters and resource status of a cell, to configure thefirst sidelink bearer to use radio resources based on a mode 1operation. In an example, the first wireless device may receive, fromthe first base station, an information request for a sidelink bearerthat is configured to use radio resources based on the mode 2 operation.The sending by the wireless device the first bearer configurationparameters may be based on the information request. The first wirelessdevice may receive, from the first base station, a radio resourcecontrol (RRC) configuration message comprising second bearerconfiguration parameters indicating that the first sidelink bearer isconfigured to use radio resources based on a mode 1 operation. The firstwireless device may send transport blocks of the first sidelink bearervia radio resources that are assigned based on the mode 1 operation.

In an example, as shown in FIG. 31 and/or FIG. 33, the first basestation may send the first bearer configuration parameters to a secondbase station (e.g., via a handover request message/secondary nodeconfiguration request message). The first base station may receive, fromthe second base station (e.g., via a handover request acknowledgemessage/secondary node configuration request acknowledge message), thesecond bearer configuration parameters determined based on the firstbearer configuration parameters. The second bearer configurationparameters that the wireless device received via the RRC configurationmessage may be the second bearer configuration parameters that the firstbase station received from the second base station. In an example, theRRC configuration message may be a handover command message indicating ahandover to a cell of the second base station.

In an example, the first wireless device may establish a PC5 RRCconnection with the second wireless device. For a direct sidelinkcommunication, the first wireless device may send a direct communicationrequest to the second wireless device, and the first wireless device mayreceive a direct communication response in response to the directcommunication request. For a direct sidelink communication, the firstwireless device may receive a direct communication request from thesecond wireless device, and the first wireless device may receive adirect communication response in response to the direct communicationrequest. Based on the direct sidelink communication, the first wirelessdevice may send, to the second wireless device, first sidelinkcapability information of the first wireless device, and/or may receive,from the second wireless device, second sidelink capability informationof the second wireless device. Based on the direct sidelinkcommunication, the first wireless device may send, to the secondwireless device, one or more first PC5-RRC configuration parameters toconfigure the PC5 RRC connection between the first wireless device andthe second wireless device. Based on the direct sidelink communication,the first wireless device may receive, from the second wireless device,one or more second PC5-RRC configuration parameters to configure the PC5RRC connection.

In an example, the first wireless device may establish a first sidelinkbearer between the first wireless device and the second wireless device.The first sidelink bearer may be based on the PC5 RRC connection. Thefirst sidelink bearer may be configured to use radio resources based ona mode 2 operation. The first sidelink bearer may be forunicast/multicast/broadcast to at least one wireless device comprisingthe second wireless device. In an example, the first wireless device mayestablish one or more sidelink bearers (e.g., one or more sidelinklogical channels, one or more QoS flows, one or more sidelink PDUsessions, etc.) comprising the first sidelink bearer and/or a secondsidelink bearer between the first wireless device and the secondwireless device. The one or more sidelink bearers may be based on thePC5 RRC connection between the first wireless device and the secondwireless device. The one or more sidelink bearers (and/or secondsidelink bearer) may be configured to use radio resources based on themode 2 operation.

In an example, the establishing the first sidelink bearer may be basedon at least one system information block of a cell of the first basestation.

In an example, the establishing the first sidelink bearers (e.g., and/orthe one or more sidelink bearers) may comprise: sending, by the firstwireless device to the second wireless device, a bearer configurationrequest (e.g., configuration request, PC5-RRC bearer configurationrequest, etc.) for establishment of the first sidelink bearer;receiving, by the first wireless device from the second wireless device,a bearer configuration response (e.g., configuration acknowledge,PC5-RRC bearer configuration response, etc.) indicating completion ofthe establishment/configuration of the first sidelink bearer (e.g.,and/or the one or more sidelink bearers) in response to the bearerconfiguration request; and/or the like. The sending the bearerconfiguration request may comprise sending the bearer configurationrequest via at least one of: a PC5 radio resource control message; aPC5-RRC configuration/reconfiguration request message; a PC5-RRC UEinformation message; a direct communication request message; and/or thelike.

In an example, the first wireless device may send, to the secondwireless device (e.g., via a first PC5-RRC message), the bearerconfiguration request requesting establishment/setup of the one or moresidelink bearers comprising the first sidelink bearer and/or the secondsidelink bearer. The bearer configuration request may comprise QoSparameters of the one or more sidelink bearers. In an example, the oneor more first PC5-RRC configuration parameters may comprise parametersof the bearer configuration request for the one or more sidelinkbearers. The first wireless device may receive, from the second wirelessdevice (e.g., via a second PC5-RRC message), the bearer configurationresponse indicating configuration of the one or more sidelink bearers.In an example, the one or more second PC5-RRC configuration parametersmay comprise parameters of the bearer configuration response for the oneor more sidelink bearers.

In an example, the QoS parameters of the one or more sidelink bearers(e.g., the one or more sidelink logical channels, one or more QoS flows,etc.) comprising the first sidelink bearer and/or the second sidelinkbearer may indicate a priority level of a sidelink bearer of the one ormore sidelink bearers. In an example, the QoS parameters of the one ormore sidelink bearers may comprise at least one of: PC5 QoS flowidentifier (PFI), PC5 5QI (e.g. PQI and Range), V2X service type (e.g.PSID or ITS-AID), QoS Class Identifier (QCI), 5G QoS Indicator (5QI:dynamic and/or non-dynamic), priority level, allocation and retentionpriority (ARP: priority level, pre-emption capability, pre-emptionvulnerability, etc.), latency requirement (e.g., tolerable packettransmission latency/delay), reliability requirement (e.g., maximumerror rate), session aggregate maximum bit rate (AMBR), bearer type(e.g., PDU session type, QoS flow type, bearer type indicating at leastone of: IP, non-IP, ethernet, IPv4, IPv6, IPv4v6, unstructured, etc.),QoS flow identifier, bearer identifier, QoS flow level QoS parameters,bearer level QoS parameters, averaging window, maximum data burstvolume, packet delay budget, packet error rate, delay criticalindication (e.g., critical or non-critical), maximum flow bit rate,guaranteed flow bit rate, notification control (e.g., indicatingnotification requested to the first base station based on events),maximum packet loss rate, and/or the like. As shown in FIG. 32, one ormore QoS flows and/or the one or more sidelink bearers may be configuredbased on the QoS parameters (e.g., PC5 QoS rules).

In an example, the establishing the one or more sidelink bearers maycomprise: sending, by the first wireless device to the first basestation, a sidelink bearer configuration request (e.g., uplink RRCmessage, information message, etc.) requestingestablishment/configuration of the first sidelink bearer (and/or the oneor more sidelink bearers); receiving, by the first wireless device fromthe first base station, a sidelink bearer configuration response (e.g.,downlink RRC message, configuration message, etc.) indicating that thefirst sidelink bearer (and/or the one or more sidelink bearers isconfigured to use radio resources based on the mode 2 operation; and/orthe like.

In an example, the first wireless device may send, to the first basestation (e.g., via an uplink RRC message), the sidelink bearerconfiguration request indicating the one or more sidelink bearers forestablishment. The sidelink bearer configuration request may comprisethe QoS parameters of the one or more sidelink bearers. The firstwireless device may receive, from the first base station (e.g., via adownlink RRC message) in response to the sidelink bearer configurationrequest, the sidelink bearer configuration response comprisingconfiguration parameters for the one or more sidelink bearers. Theconfiguration parameters may comprise the QoS parameters of the one ormore sidelink bearers. The first wireless device may configure the oneor more sidelink bearers with the second wireless device based on theconfiguration parameters in the sidelink bearer configuration responsereceived from the first base station. The first wireless device maysend, to the second wireless device, the bearer configuration request(e.g., the PC5-RRC bearer configuration request; e.g., via a firstPC5-RRC message) based on the configuration parameters in the sidelinkbearer configuration response from the first base station.

In an example, the establishing the first sidelink bearer (and/or theone or more sidelink bearers) may be performed when the first wirelessdevice is at least one of: in an RRC idle state; in an RRC inactivestate; when served by a base station other than the first base station;and/or the like.

In an example, the mode 2 operation may comprise selecting a radioresource for transmission of a transport block for the first sidelinkbearer (e.g., the one or more sidelink bearers) from a mode 2 resourcepool. In an example, the mode 2 operation may comprise selecting by thefirst wireless device a radio resource for transmission of a transportblock for the first sidelink bearer. The first wireless device mayreceive a resource selection policy for the mode 2 operation from thefirst base station via one or more system information blocks and/or adedicated RRC message. The first wireless device may select a radioresource for transmission of a transport block for the first sidelinkbearer based on the resource selection policy.

In an example, the establishing the one or more sidelink bearers (e.g.,comprising the first sidelink bearer and/or the second sidelink bearer)may comprise configuring/determining first bearer configurationparameters of the first sidelink bearer (e.g., and/or of the one or moresidelink bearers). The first bearer configuration parameters maycomprise parameters for using radio resources to transmit transportblocks of the first sidelink bearer (e.g., and/or of the one or moresidelink bearers) based on the mode 2 operation. In an example, theestablishing the one or more sidelink bearers (e.g., comprising thefirst sidelink bearer and/or the second sidelink bearer) may comprisetransmitting the first bearer configuration parameters to the secondwireless device (e.g., via the bearer configuration request and/or thePC5-RRC bearer configuration request). The first wireless device mayreceive the first bearer configuration parameters from a base station(e.g., the first base station).

In an example, the first wireless device may send, based on the firstbearer configuration parameters, transport blocks of the first sidelinkbearer (e.g., and/or the one or more sidelink bearers) via radioresources that are selected based on the mode 2 operation (e.g., via aresource pool for the mode 2 operation).

In an example, the first wireless device may send, to the first basestation, the first bearer configuration parameters of the first sidelinkbearer (e.g., and/or the one or more sidelink bearers, the secondsidelink bearer). The first bearer configuration parameters may indicatethat the first sidelink bearer (e.g., and/or the one or more sidelinkbearers, the second sidelink bearer) is configured to use radioresources based on the mode 2 operation. The first wireless device maysend, to the first base station, bearer configuration parameters of thesecond sidelink bearer. In an example, the first wireless device maysend, to the first base station, the first bearer configurationparameters via at least one RRC message (e.g., UE information message,UE information response message, UE assistance information message, RRCsetup request/complete message, RRC reestablishment request/completemessage, RRC resume request/complete message, RRC reconfigurationcomplete message, etc.).

In an example, the first wireless device may transition from an RRC idlestate or an RRC inactive state to an RRC connected state by performing arandom access to a cell (e.g., the first cell) of the first base stationand/or by establishing an RRC connection with the first base station.Based on the RRC connection with the first base station, the firstwireless device may send, to the first base station, the first bearerconfiguration parameters of the first sidelink bearer. In an example,the first wireless device may establish/setup the first sidelink bearerand/or the one or more sidelink bearers based on pre-configuredparameters or at least one system information block received from a basestation (e.g., the first base station) when the first wireless device isin the RRC idle state or the RRC inactive state.

In an example, the first wireless device may receive, from the firstbase station, an information request for a sidelink bearer that isconfigured to use radio resources based on the mode 2 operation. Thesending by the wireless device the first bearer configuration parametersmay be based on and/or in response to the information request. The firstwireless device may receive the information request via at least onedownlink RRC message (e.g., UE information request message, UEassistance information request message, RRC setup message, RRCreestablishment message, RRC resume message, RRC reconfigurationmessage, etc.).

In an example, the information request may indicate at least one reportcondition to determine whether to send bearer configuration parametersof a sidelink bearer that is configured to use radio resources based onthe mode 2 operation. The first wireless device may send, to the firstbase station, the first bearer configuration parameters of the firstsidelink bearer and/or the one or more sidelink bearers based on and/orin response to at least one of the at least one report condition of theinformation request being met/satisfied. The at least one reportcondition may comprise at least one of: a quality-of-service (QoS)requirement; a channel busy ratio (CBR) of a resource pool for the mode2 operation; a channel occupancy ratio (CR) of the first wireless devicefor a resource pool configured for the mode 2 operation; a channeloccupancy ratio (CR) of the sidelink bearer for a resource poolconfigured for the mode 2 operation; a received signal strengthindicator (RSSI) of sidelink radio resources; and/or the like.

In an example, the at least one report condition may indicate thatsending bearer configuration parameters of a sidelink bearer with themode 2 operation is required/needed if the QoS requirement (e.g.,latency requirement, data throughput/bandwidth requirement, reliabilityrequirement, etc.) of the sidelink bearer with the mode 2 operation isnot met/satisfied with resource allocation employing the mode 2operation and/or with a resource pool for the mode 2 operation. The QoSrequirement may comprise one or more elements of the QoS parameters ofthe one or more sidelink bearers that is transmitted via the bearerconfiguration request from the first wireless device to the secondwireless device.

In an example, the at least one report condition may indicate thatsending bearer configuration parameters of a sidelink bearer with themode 2 operation is required/needed if the CBR of the resource pool forthe mode 2 operation is equal to or larger than a threshold value (e.g.,80%). In an example, the at least one report condition may indicate thatsending bearer configuration parameters of a sidelink bearer with themode 2 operation is required/needed if the CR of the first wirelessdevice (e.g., channel occupancy ratio of traffic of the first wirelessdevice) for the resource pool configured for the mode 2 operation isequal to or larger than a threshold value (e.g., 40%). In an example,the at least one report condition may indicate that sending bearerconfiguration parameters of a sidelink bearer with the mode 2 operationis required/needed if the CR of the sidelink bearer (e.g., the one ormore sidelink bearers, the first sidelink bearer, the second sidelinkbearer, etc.) (e.g., channel occupancy ratio of traffic of the sidelinkbearer) for the resource pool configured for the mode 2 operation isequal to or larger than a threshold value (e.g., 30%). The at least onereport condition may indicate that sending bearer configurationparameters of a sidelink bearer with the mode 2 operation isrequired/needed if the RSSI of sidelink radio resources (e.g., radioresources indicated in the information request for the sidelinkresource; the resource pool for the mode 2 operation) is equal to orlarger than a threshold value (e.g., 90%).

In an example, the first bearer configuration parameters may indicatethat one or more of the QoS requirement for the first sidelink bearerand/or the one or more sidelink bearer are not met/satisfied based onthe mode 2 operation. In an example, the first bearer configurationparameters may indicate that a CBR of the resource pool for the mode 2operation is equal to or larger than a value. In an example, the firstbearer configuration parameters may indicate that a CR of the firstwireless device (e.g., channel occupancy ratio of traffic of the firstwireless device) for the resource pool configured for the mode 2operation is equal to or larger than a value. In an example, the firstbearer configuration parameters may indicate that a CR of the firstsidelink bearer (e.g., the one or more sidelink bearers, the secondsidelink bearer, etc.) (e.g., channel occupancy ratio of traffic of thesidelink bearer) for the resource pool configured for the mode 2operation is equal to or larger than a value. In an example, the firstbearer configuration parameters may indicate that an RSSI of sidelinkradio resources (e.g., radio resources indicated in the informationrequest for the sidelink resource; the resource pool for the mode 2operation) is equal to or larger than a value.

In an example, the first bearer configuration parameters may indicatethat the first sidelink bearer and/or the one or more sidelink bearer(e.g., the second sidelink bearer) is configured to use radio resourcesbased on the mode 2 operation. The first bearer configuration parametersmay indicate at least one of: a bearer identifier of the first sidelinkbearer and/or the one or more sidelink bearer; a QoS requirement (e.g.,the QoS parameters of the one or more sidelink bearers that istransmitted via the bearer configuration request from the first wirelessdevice to the second wireless device) of the first sidelink bearerand/or the one or more sidelink bearers (e.g., the QoS requirementcomprising at least one of: 5QI, ARP, bit rate, throughput, Prioritylevel, transmission latency, packet loss rate, etc.); measured QoSvalues for one or more of the QoS parameters (e.g., measured/monitoredbit rate or throughput, measured/monitored packet transmission latency,measured/monitored packet loss rate, etc.); a CR of the first sidelinkbearer and/or the first wireless device (e.g., for a resource poolconfigured for the mode 2 operation); a CBR/RSSI of a resource poolconfigured for the mode 2 operation; a field (e.g., cast type)indicating whether the first sidelink bearer is for a unicasttransmission, a multicast (e.g., group cast) transmission, and/or abroadcast transmission; a service type; network slice information;performance measurement results of the first sidelink bearer (e.g., theperformance measurement results indicating at least one of: whether theQoS requirement is met based on a mode 2 operation; measuredquality-of-service information; measured packet loss rate; measuredlatency; measured throughput; etc.); a destination identifier of thefirst sidelink bearer (e.g., the destination identifier indicating atleast one of: a service associated with the first sidelink bearer, thesecond wireless device, layer 2 identifier, and/or the like); (average)ProSe per-packet priority (PPPP); (average) ProSe per-packet reliability(PPPR); a resource pool that is used for the first sidelink bearerand/or the one or more sidelink bearers; at least one QoS flow mapped tothe first sidelink bearer and/or the one or more sidelink bearers; atleast one PDU session mapped to the first sidelink bearer and/or the oneor more sidelink bearers; and/or the like.

In an example, the first bearer configuration parameters may comprise atleast one of:

-   -   a bearer identifier (e.g., SLRB Identity) of a sidelink bearer        (e.g., for unicast/groupcast/broadcast) for at least one of        transmission and/or reception;    -   a destination identifier of a sidelink bearer (e.g., for        unicast/groupcast/broadcast) for at least one of transmission        and/or reception;    -   a cast type of a sidelink bearer (e.g., for        unicast/groupcast/broadcast) for at least one of transmission        and/or reception;    -   a list of at least one QoS flow mapped to a sidelink bearer        (e.g., for unicast/groupcast/broadcast) for at least one of        transmission and/or reception;    -   a transmission range of a sidelink bearer (e.g., based on        distance to a destination wireless device);    -   a discard timer (e.g., for packet discard) of a sidelink bearer        (e.g., for unicast/groupcast/broadcast) for at least one of        transmission and/or reception;    -   a PDCP sequence number (SN) size of a wireless device and/or a        sidelink bearer (e.g., for unicast/groupcast/broadcast) for at        least one of transmission and/or reception;    -   a maximum context identifier (e.g., maxCID) of a wireless device        and/or a sidelink bearer (e.g., for unicast/groupcast/broadcast)        for at least one of transmission and/or reception;    -   a robust header compression (ROHC) profile of a wireless device        and/or sidelink bearer;    -   a T-reordering timer of a sidelink bearer (e.g., for        unicast/groupcast/broadcast) for at least one of transmission        and/or reception;    -   an OutOfOrderDelivery indication of a sidelink bearer (e.g., for        unicast/groupcast/broadcast) for at least one of transmission        and/or reception;    -   an RLC mode of a sidelink bearer (e.g., for        unicast/groupcast/broadcast) for at least one of transmission        and/or reception;    -   an RLC SN field length of a sidelink bearer (e.g., for        unicast/groupcast/broadcast) for at least one of transmission        and/or reception;    -   a T-Reassembly timer (e.g., timer for reassembly) of a sidelink        bearer (e.g., for unicast/groupcast/broadcast) for at least one        of transmission and/or reception;    -   a T-PollRetransmit timer of a sidelink bearer (e.g., for        unicast/groupcast/broadcast) for at least one of transmission        and/or reception;    -   a PollPDU of a sidelink bearer (e.g., for        unicast/groupcast/broadcast) for at least one of transmission        and/or reception (e.g., for RLC AM, value p4 may correspond to 4        PDUs, value p8 may correspond to 8 PDUs and/or the like,        infinity may correspond to an infinite number of PDUs);    -   a PollByte is of a sidelink bearer (e.g., for        unicast/groupcast/broadcast) for at least one of transmission        and/or reception (e.g., for RLC AM, value kB25 may correspond to        25 kBytes, value kB50 may correspond to 50 kBytes and/or the        like, infinity may correspond to an infinite amount of kBytes);    -   a MaxRetxThreshold (e.g., maximum number of retransmission) of a        sidelink bearer (e.g., for unicast/groupcast/broadcast) for at        least one of transmission and/or reception;    -   a T-StatusProhibit timer (e.g., timer for status reporting) of a        sidelink bearer (e.g., for unicast/groupcast/broadcast) for at        least one of transmission and/or reception;    -   a LogicalChannelldentity of a sidelink bearer (e.g., for        unicast/groupcast/broadcast) for at least one of transmission        and/or reception;    -   a LogicalChannelGroup of a sidelink bearer (e.g., for        unicast/groupcast/broadcast) for at least one of transmission        and/or reception;    -   a Priority of a sidelink bearer (e.g., for        unicast/groupcast/broadcast) for at least one of transmission        and/or reception;    -   a PrioritizedBitRate of a sidelink bearer (e.g., for        unicast/groupcast/broadcast) for at least one of transmission        and/or reception;    -   a BucketSizeDuration (e.g., logical channel bucket size        duration) of a sidelink bearer (e.g., for        unicast/groupcast/broadcast) for at least one of transmission        and/or reception;    -   a ConfiguredGrantTypelAllowed indication indicating whether a        sidelink bearer (e.g., for unicast/groupcast/broadcast) for at        least one of transmission and/or reception is allowed or not;    -   a SchedulingRequestID for a sidelink bearer (e.g., for        unicast/groupcast/broadcast) for at least one of transmission        and/or reception;    -   a LogicalChannelSR-DelayTimerApplied of a sidelink bearer (e.g.,        for unicast/groupcast/broadcast) for at least one of        transmission and/or reception;    -   HARQ related information of a sidelink bearer (e.g., for        unicast/groupcast/broadcast) for at least one of transmission        and/or reception; and/or the like.

In an example, the first base station may determine, based on the firstbearer configuration parameters and/or resource status of one or morecells (e.g., resource status of the first cell, resource status ofresource pool for the mode 1 operation, resource status of resource poolfor the mode 2 operation, resource status of the first base station,etc.), to configure/switch/change the first sidelink bearer and/or theone or more sidelink bearers to use radio resources based on a mode 1operation. In an example, the first base station may determine secondbearer configuration parameters indicating that the first sidelinkbearer is configured to use radio resources based on the mode 1operation.

In an example, as shown in FIG. 31 and/or FIG. 33, the first basestation may receive, from the first wireless device, a measurementresult (e.g., via at least one measurement report, one or more RRCmessages, etc.) of the second cell of the second base station. Themeasurement result may comprise RSRP, RSRQ, and/or SINR of the firstcell (e.g., one or more beams of the first cell), the second cell (e.g.,one or more beams of the second cell), and/or one or more cells (e.g.,one or more beams of the one or more cells). The first base station maydetermine, based on the measurement result, to initiate a handover or asecondary node configuration of the first wireless device to the secondcell of the second base station. The first base station may send ahandover request (e.g., handover request message, handover requiredmessage, etc.) for the handover of the first wireless device to thesecond base station (e.g., via the direct interface or the indirectinterface between the first base station and the second base station).The first base station may send a secondary node (S-node) configurationrequest (e.g., secondary node addition request message, secondary nodemodification request message, etc.) for the secondary node configurationof the first wireless device with the second base station via the directinterface between the first base station and the second base station.The first base station may send the first bearer configurationparameters to the second base station (e.g., via the handover requestmessage and/or via the secondary node configuration request message).The handover request and/or the secondary node configuration request maycomprise the first bearer configuration parameters and/or a wirelessdevice identifier of the first wireless device and/or the secondwireless device. The handover request and/or the secondary nodeconfiguration request may comprise first RRC configuration parameters ofthe first wireless device. The first RRC configuration parameters may beconfigured by the first base station.

In an example, the second base station may determine, based on the firstbearer configuration parameters, the first wireless device, the secondwireless device, and/or the first RRC configuration parameters of thefirst wireless device, to accept the handover request and/or thesecondary node configuration request for the first wireless device. Inan example, the second base station may determine, based on the firstbearer configuration parameters (e.g., based on the handover requestand/or the secondary node configuration request) and/or resource statusof one or more cells (e.g., resource status of the second cell, resourcestatus of resource pool for the mode 1 operation, resource status ofresource pool for the mode 2 operation, resource status of the secondbase station, etc.), to configure/switch/change/accept the firstsidelink bearer and/or the one or more sidelink bearers to use radioresources based on the mode 1 operation. In an example, the second basestation may determine the second bearer configuration parametersindicating that the first sidelink bearer and/or the one or moresidelink bearers is configured to use radio resources based on the mode1 operation. In an example, the second base station may determine, basedon the first bearer configuration parameters (e.g., based on thehandover request and/or the secondary node configuration request), thesecond bearer configuration parameters for the wireless device.

In an example, the second base station may send, to the first basestation, a response (e.g., via a handover request acknowledge message,via a secondary node configuration request acknowledge message, and/orvia an RRC reconfiguration message) for the handover request and/or thesecondary node configuration request. The handover request acknowledgemessage and/or the secondary node configuration request acknowledgemessage may comprise the RRC reconfiguration message. The first basestation may receive, from the second base station, the second bearerconfiguration parameters determined based on the first bearerconfiguration parameters. The second bearer configuration parameters mayindicate that the first sidelink bearer and/or the one or more sidelinkbearers are configured to use radio resources based on the mode 1operation. The first base station may receive, from the second basestation, the response for the handover request and/or the secondary nodeconfiguration request. The response for the handover request and/or thesecondary node configuration request may comprise at least one of: thesecond bearer configuration parameters for the first sidelink bearerand/or the one or more sidelink bearers, the wireless device identifierof the first wireless device and/or the second wireless device, secondRRC configuration parameters (e.g., the RRC reconfiguration message) ofthe first wireless device, and/or the like. The second RRC configurationparameters may be configured by the second base station. In an example,an RRC reconfiguration message from the second base station to the firstbase station for the first wireless device may comprise the second RRCconfiguration parameters.

In an example, the mode 1 operation (e.g., assigning sidelink resourcesbased on dynamic grant) may comprise at least one of: sending, by thefirst wireless device to a base station (e.g., the first base station orthe second base station), a grant request for the first sidelink bearerand/or the one or more sidelink bearers (e.g., the grant request maycomprise at least one of a buffer status report or a schedulingrequest); receiving, from the base station (e.g., the first base stationor the second base station) and based on the grant request, a sidelinkgrant indicating a radio resource for transmitting a transport block ofthe first sidelink bearer and/or the one or more sidelink bearers;and/or the like. In an example, the mode 1 operation (e.g., type1/2configured grant, semi-persistent scheduling, etc.) may comprise atleast one of: receiving, by the first wireless device from the basestation (e.g., the first base station or the second base station),resource configuration parameters indicating configured grant resources(e.g., a type 1 configured grant resources, a type 2 configured grantresources, and/or semi-persistent scheduling resources, etc.); selectinga radio resource from the configured grant resources for packettransmission of the first sidelink bearer and/or the one or moresidelink bearers; and/or the like.

In an example, the one or more cells may comprise at least one of: thefirst cell of the first base station, a primary cell (e.g., primarycell, primary secondary cell, PScell, special cell, Spcell, etc.) of thefirst wireless device, secondary cells (e.g., of MCG or SCG) of thefirst wireless device, the second cell of the second base station (e.g.,a handover target base station or a secondary base station of the firstwireless device), at least one cell of the first base station and/or thesecond base station, and/or the like. The resource status of the one ormore cells may comprise at least one of: traffic load (e.g., trafficamount comparing to a capacity of a base station, a cell, a resourcepool, etc.), hardware load (e.g., CPU, memory, storage, buffer, backhaullink, antenna, etc.), radio resource occupancy ratio (e.g., of the oneor more cells, resource pool of the one or more cells for mode 1operation or mode 2 operation, etc.), a hardware/software/resource load,network capacity (e.g., capacity of a base station, a cell, a resourcepool, etc.), and/or the like.

In an example, the first base station and/or the second base station maydetermine to configure/switch/change the first sidelink bearer and/orthe one or more sidelink bearers to use radio resources based on themode 1 operation based on one or more elements of the QoS requirement ofthe first sidelink bearer and/or the one or more sidelink bearers notbeing met/satisfied with the mode 2 operation.

If the first bearer configuration parameters indicate that a latencyrequirement of the first sidelink bearer and/or the one or more sidelinkbearers is not met (e.g., the latency requirement is 1 ms, and ameasured latency is 1.5 ms), the first base station and/or the secondbase station may determine to configure the first sidelink bearer and/orthe one or more sidelink bearers to use the mode 1 operation.

If the first bearer configuration parameters indicate that a packet lossrate requirement of the first sidelink bearer and/or the one or moresidelink bearers is not met (e.g., the packet loss rate requirement is0.000001%, and a measured packet loss rate is 0.1%), the first basestation and/or the second base station may determine to configure thefirst sidelink bearer and/or the one or more sidelink bearers to use themode 1 operation.

If the first bearer configuration parameters indicate that atransmission bit rate or throughput requirement of the first sidelinkbearer and/or the one or more sidelink bearers is not met (e.g., thetransmission bit rate or throughput requirement is 100 kbps, and ameasured transmission bit rate or throughput is 50 kbps), the first basestation and/or the second base station may determine to configure thefirst sidelink bearer and/or the one or more sidelink bearers to use themode 1 operation.

In an example, the first base station and/or the second base station maydetermine to configure/switch/change the first sidelink bearer and/orthe one or more sidelink bearers to use radio resources based on themode 1 operation based on at least one of: a CBR of the resource poolfor the mode 2 operation is equal to or larger than a value; a CR of thefirst wireless device (e.g., channel occupancy ratio of traffic of thefirst wireless device) for the resource pool configured for the mode 2operation is equal to or larger than a value; a CR of the first sidelinkbearer (e.g., the one or more sidelink bearers, the second sidelinkbearer, etc.) (e.g., channel occupancy ratio of traffic of the sidelinkbearer) for the resource pool configured for the mode 2 operation isequal to or larger than a value; an RSSI of sidelink radio resources(e.g., radio resources indicated in the information request for thesidelink resource; the resource pool for the mode 2 operation) is equalto or larger than a value; and/or the like. In an example, the resourcepool for the mode 2 operation may be a resource pool of the one or morecells (e.g., a cell of the first base station and/or the second basestation; the first cell; the second cell; etc.) of the first basestation and/or the second base station.

In an example, the first base station and/or the second base station maydetermine to configure/switch/change the first sidelink bearer and/orthe one or more sidelink bearers to use radio resources based on themode 1 operation if one or more elements (e.g., latency, packet lossrate, transmission bit rate, transmission throughput, priority level,etc.) of the QoS requirement of the first sidelink bearer and/or the oneor more sidelink bearers are equal to or larger than a threshold value(e.g., if a latency requirement is smaller than a latency thresholdvalue; if a packet loss rate requirement is smaller than a packet lossrate threshold value; if a transmission bit rate or throughputrequirement is larger than a transmission bit rate or throughputthreshold value; if a priority level requirement is higher than apriority level threshold value; etc.).

In an example, the first base station and/or the second base station maydetermine to configure/switch/change the first sidelink bearer and/orthe one or more sidelink bearers to use radio resources based on themode 1 operation based on resource status of one or more cells (e.g.,resource status of resource pool for the mode 1 operation, resourcestatus of resource pool for the mode 2 operation, resource status of abase station, resource status of the first cell and/or the second cell,etc.) of the first base station and/or the second base station. Thefirst base station and/or the second base station may determine toconfigure/switch/change the first sidelink bearer and/or the one or moresidelink bearers to use radio resources based on the mode 1 operation ifat least one of a traffic load (e.g., measured traffic amount comparedto a capacity of a base station, a cell, a resource pool, etc.) of aresource pool (e.g., for mode 1 operation or mode 2 operation), a cell(e.g., the one or more cell, the first cell, the second cell) or a basestation (e.g., the first base station and/or the second base station); ahardware load (e.g., CPU, memory, storage, buffer, backhaul link,antenna, etc.); a radio resource occupancy ratio (e.g., resourceutilization of uplink/downlink resources and/or sidelink resources formode 1 operation, etc.); and/or a hardware/software/resource load of thefirst base station and/or the second base station is equal to or smallerthan a threshold value. In an example, the first base station and/or thesecond base station may determine to configure/switch/change the firstsidelink bearer and/or the one or more sidelink bearers to use radioresources based on the mode 1 operation if network capacity (e.g.,capacity of a base station, a cell, a resource pool, etc.) of the firstbase station and/or the second base station is equal to or larger than avalue.

In an example, the second bearer configuration parameters may indicateat least one of: configured grant resources (e.g., type 1 configuredgrant, type 2 configured grant, semi-persistent scheduling, etc.);dynamic grant configuration parameters (e.g., SR, BSR transmissionconfiguration parameters); a mode 1 resource pool (e.g., resource poolindex, resource configuration parameters, frequency/time domaininformation); a cell identifier of a cell associated with the mode 1resource pool; and/or the like. The second bearer configurationparameters may comprise at least one updated parameter from the firstbearer configuration parameters. The first base station and/or thesecond base station may update/reconfigure one or more elements of thefirst bearer configuration parameters to the at least one updatedparameter that the second bearer configuration parameters comprise.

In an example, parameters for the configured grant resources indicatedin the second bearer configuration parameters may comprise at least oneof:

-   -   an antenna port (e.g., antennaPort) indicating antenna port(s)        to be used for the configured grant resources, and/or the        maximum bitwidth is 5;    -   a configured grant DMRS configuration (e.g.,        cg-DMRS-Configuration) indicating DMRS configuration;    -   a configured grant timer (e.g., configuredGrantTimer) indicating        an initial value of the configured grant timer in multiples of        periodicity;    -   a DMRS sequence initialization (e.g., dmrs-SeqInitialization)        that the first base station or the second base station        configures if transformPrecoder is disabled;    -   a frequency domain allocation (e.g., frequencyDomainAllocation)        indicating a frequency domain resource allocation;    -   a frequency hopping configuration (e.g., frequencyHopping) in        which a value intraSlot may enable ‘Intra-slot frequency        hopping’ and a value interSlot may enable ‘Inter-slot frequency        hopping’, if the field is absent, frequency hopping may not be        configured;    -   a frequency hopping offset (e.g., frequencyHoppingOffset) that        may enable intra-slot frequency hopping with the given frequency        hopping offset;    -   a modulation coding scheme table (e.g., mcs-Table) indicating a        modulation coding scheme (MCS) the first wireless device uses        for PUSCH and/or PSSCH without transform precoding, if the field        is absent the first wireless device may apply a 64 QAM; a        modulation coding scheme table transform precoder (e.g.,        mcs-TableTransformPrecoder) indicating an MCS table the first        wireless device uses for PUSCH with transform precoding, if the        field is absent the first wireless device may apply a 64 QAM;    -   a modulation coding scheme and transport block size (e.g.,        mcsAndTBS) indicating a modulation order, target code rate,        and/or TBsize;    -   a number of HARQ process (e.g., nrofHARQ-Processes) that may be        applied for Type 1 and/or Type 2;    -   a p0 PUSCH/PSSCH alpha (e.g., p0-PUSCH-Alpha, p0-PSSCH-Alpha)        indicating an index of a P0-PUSCH-AlphaSet or P0-PSSCH-AlphaSet        used for the configured grant resources;    -   a periodicity for UL and/or sidelink transmission without UL        and/or sidelink grant for type 1 and type 2;    -   a power control loop to use (e.g., powerControlLoopToUse)        indicating a closed control loop to apply;    -   a resource block group size (e.g., rbg-Size) indicating a        selection between configuration 1 and configuration 2 for        resource block group (RBG) size for PUSCH and/or PSSCH, the        first wireless device may not apply this field if        resourceAllocation is set to resourceAllocationType1, the first        wireless device may apply the value config1 when the field is        absent (e.g., rbg-Size may be used when a transformPrecoder        parameter is disabled);    -   a repetition K redundancy version (e.g., repK-RV) indicating a        redundancy version (RV) sequence to use, the first base station        or the second base station may configure this field if        repetitions are used (e.g., if repK may be set to n2, n4 or n8);    -   a repetition K (e.g., repK) indicating a number of repetitions        of K;    -   a resource allocation (e.g., resourceAllocation) indicating a        configuration of resource allocation type 0 and/or resource        allocation type 1 (e.g., for Type 1 UL or sidelink data        transmission without grant, resourceAllocation may be        resourceAllocationType0 or resourceAllocationType1);    -   an RRC configured uplink/sidelink grant (e.g.,        rrc-ConfiguredUplinkGrant, rrc-ConfiguredSidelinkGrant)        indicating a configuration for “configured grant” transmission        with fully RRC-configured UL grant (Type1) (e.g., if this field        is absent the first wireless device may use UL or sidelink grant        configured by DCI addressed to CS-RNTI (Type2)) (e.g., Type 1        configured grant may be configured for sidelink, UL, and/or        SUL);    -   a sounding reference signal resource indicator (e.g.,        srs-ResourceIndicator) indicating an SRS resource to be used;    -   a time domain allocation (e.g., timeDomainAllocation) indicating        a combination of start symbol and length and PUSCH or PSSCH        mapping type;    -   a time domain offset (e.g., timeDomainOffset) indicating an        offset related to system frame number (SFN)=0;    -   a transform precoder (e.g., transformPrecoder) enabling or        disabling transform precoding for type1 and type2 (e.g., if the        field is absent, the first wireless device may enable or disable        transform precoding in accordance with the field        msg3-transformPrecoder in RACH-ConfigCommon;    -   an uplink/sidelink control information on PUSCH/PSSCH (e.g.,        uci-OnPUSCH or sci-OnPSSCH) indicating a selection between and        configuration of dynamic and semi-static beta-offset (e.g., for        Type 1 UL or sidelink data transmission without grant,        uci-OnPUSCH and/or sci-OnPSSCH may be set to semiStatic); and/or        the like.

In an example, the first wireless device may receive, from the firstbase station, an RRC configuration message comprising the second bearerconfiguration parameters. In an example, the second bearer configurationparameters may indicate that the first sidelink bearer and/or the one ormore sidelink bearers are configured to use radio resources based on themode 1 operation. The second bearer configuration parameters that thefirst wireless device receives (e.g., via RRC configuration messageand/or RRC reconfiguration message) may be determined by the first basestation. The second bearer configuration parameters that the firstwireless device receives (e.g., via RRC configuration message, RRCreconfiguration message, and/or handover command message) may be thesecond bearer configuration parameters that the first base stationreceived from the second base station. In an example, the RRCconfiguration message may be a handover command message (e.g.,comprising the RRC reconfiguration message from the second base stationto the first base station) indicating a handover for the first wirelessdevice to a cell (e.g., the second cell) of the second base station. Thehandover command message may be based on the message (e.g., the handoverrequest acknowledge message/the secondary node configuration requestacknowledge message) received from the second base station (e.g., viathe direct interface and/or the indirect interface). The second basestation may assign, radio resources for the first sidelink bearer of thefirst wireless device based on the second bearer configurationparameters. In an example, the RRC configuration message may be at leastone of: an RRC reconfiguration message; an RRC resume message; an RRCsetup message; an RRC reestablishment message; a handover commandmessage; and/or the like.

In an example, the RRC configuration message and/or the second bearerconfiguration parameters may comprise at least one parameter indicatingthat at least one third bearers configured to use the mode 2 operation(e.g., that is indicated in the first bearer configuration parameters)is kept using the mode 2 operation.

In an example, the first wireless device may send, to the secondwireless device and based on the second bearer configuration parameters,a configuration modification request for modification of the firstsidelink bearer and/or the one or more sidelink bearers. Theconfiguration modification request may be a PC5-RRC message (e.g.,PC5-RRC reconfiguration message, PC5-RRC bearer modification message,etc.). The configuration modification request may comprise the secondbearer configuration parameters. The first wireless device may receive,from the second wireless device, a configuration modificationacknowledge indicating completion of the modification of the firstsidelink bearer and/or the one or more sidelink bearers.

In an example, if the RRC configuration message that the first wirelessdevice receives from the first base station is a handover command, thefirst wireless device may perform, based on the RRC configurationmessage, a random access (e.g., by sending one or more random accesspreambles and receiving one or more random access responses via thecell) to the cell (e.g., the second cell) of the second base station foran RRC connection with (e.g., handover to) the second base station. TheRRC configuration message may be associated with the RRC connection withthe second base station. In an example, if the RRC configuration messagethat the first wireless device receives from the first base station is ahandover command, the first wireless device may send, based on the RRCconfiguration message and/or the random access, an uplink RRC message(e.g., RRC reconfiguration complete message) to the second base stationfor the RRC connection with the second base station.

In an example, the first wireless device may send, based on the secondbearer configuration parameters, transport blocks of the first sidelinkbearer and/or the one or more sidelink bearers to the second wirelessdevice via radio resources that are assigned based on the mode 1operation and/or the second bearer configuration parameters. In anexample, the first base station (e.g., in FIG. 25) or the second basestation (e.g., in FIG. 33) may assign radio resources for the firstsidelink bearer and/or the one or more sidelink bearers of the firstwireless device based on the mode 1 operation and/or based on the secondbearer configuration parameters. In an example, the first wirelessdevice may transmit the transport blocks to the second wireless devicevia the configured grant resources configured by the second bearerconfiguration parameters. In an example, the first wireless device maysend, to the first base station or the second base station, one or morescheduling requests and/or one or more buffer status reports (e.g., viaMAC CE and/or UCI/PUCCH) for request of sidelink radio resources basedon the second bearer configuration parameters and/or based on the RRCconfiguration message. The first wireless device may receive one or moregrants indicating sidelink radio resources in response to the one ormore scheduling request and/or the one or more buffer status reports.

In an example, if the second bearer configuration parameters areconfigured by the second base station, the first wireless device mayperform the handover to the second cell of the second base station, andthe sending the transport blocks of the first sidelink bearer to thesecond wireless device based on the second bearer configurationparameters may be performed at the second cell of the second basestation.

In an example, as shown in FIG. 27, the first base station and/or thesecond base station may determine, based on resource status of a cell(e.g., the one or more cells, the first cell, the second cell, etc.), toconfigure the first sidelink bearer and/or the one or more sidelinkbearers (e.g., that is configured to use radio resources based on themode 1 operation) to use radio resources based on the mode 2 operation.The first base station and/or the second base station may send, to thefirst wireless device, a second RRC configuration message comprisingthird bearer configuration parameters indicating that the first sidelinkbearer is configured to use radio resources based on the mode 2operation. In an example, the first wireless device may receive, fromthe first base station, a configuration message (e.g., the second RRCconfiguration message) comprising the third bearer configurationparameters indicating that the first sidelink bearer and/or the one ormore sidelink bearers (e.g., the second sidelink bearer) are configuredto use radio resources based on the mode 2 operation. The first wirelessdevice may send transport blocks of the second sidelink bearer via radioresources selected based on the mode 2 operation and/or the third bearerconfiguration parameters.

In an example, the first base station and/or the second base station maydetermine to configure/switch/change the first sidelink bearer and/orthe one or more sidelink bearers to use radio resources based on themode 2 operation based on resource status of one or more cells (e.g.,resource status of resource pool for the mode 1 operation, resourcestatus of resource pool for the mode 2 operation, resource status of abase station, resource status of the first cell and/or the second cell,etc.) of the first base station and/or the second base station.

The first base station and/or the second base station may determine toconfigure/switch/change the first sidelink bearer and/or the one or moresidelink bearers to use radio resources based on the mode 2 operation ifat least one of a traffic load (e.g., measured traffic amount comparedto a capacity of a base station, a cell, a resource pool, etc.) of aresource pool (e.g., for mode 1 operation), a cell (e.g., the one ormore cell, the first cell, the second cell) or a base station (e.g., thefirst base station and/or the second base station); a hardware load(e.g., CPU, memory, storage, buffer, backhaul link, antenna, etc.); aradio resource occupancy ratio (e.g., resource utilization ofuplink/downlink resources and/or sidelink resources for the mode 1operation); and/or a hardware/software/resource load of the first basestation and/or the second base station is equal to or larger than athreshold value. In an example, the first base station and/or the secondbase station may determine to configure/switch/change the first sidelinkbearer and/or the one or more sidelink bearers to use radio resourcesbased on the mode 2 operation if network capacity (e.g., capacity of abase station, a cell, a resource pool, etc.) of the first base stationand/or the second base station is equal to or smaller than a value.

In an example, the first base station and/or the second base station maydetermine to configure/switch/change the first sidelink bearer and/orthe one or more sidelink bearers to use radio resources based on themode 2 operation based on at least one of: a CBR of the resource poolfor the mode 2 operation is equal to or smaller than a value; a CR ofthe first wireless device (e.g., channel occupancy ratio of traffic ofthe first wireless device) for the resource pool configured for the mode2 operation is equal to or smaller than a value; a CR of the firstsidelink bearer (e.g., the one or more sidelink bearers, the secondsidelink bearer, etc.) (e.g., channel occupancy ratio of traffic of thesidelink bearer) for the resource pool configured for the mode 2operation is equal to or smaller than a value; an RSSI of sidelink radioresources (e.g., radio resources indicated in the information requestfor the sidelink resource; the resource pool for the mode 2 operation)is equal to or smaller than a value; and/or the like. In an example, theresource pool for the mode 2 operation may be a resource pool of the oneor more cells (e.g., a cell of the first base station and/or the secondbase station; the first cell; the second cell; etc.) of the first basestation and/or the second base station.

In an example, as shown in FIG. 34, the handover request or thesecondary node configuration request for the first wireless device fromthe first base station to the second base station may comprise bearerconfiguration parameters of at least one sidelink bearer (e.g.,configured with the second wireless device) that is configured to usethe mode 1 operation. The second base station may determine toconfigure/switch/change the at least one sidelink bearer to use radioresources based on the mode 2 operation based on resource status of oneor more cells (e.g., resource status of resource pool for the mode 1operation, resource status of resource pool for the mode 2 operation,resource status of a base station, resource status of the second cell,etc.) of the second base station. The second base station may determineto configure/switch/change the at least one sidelink bearer to use radioresources based on the mode 2 operation if at least one of a trafficload (e.g., measured traffic amount compared to a capacity of a basestation, a cell, a resource pool, etc.) of a resource pool (e.g., formode 1 operation), a cell (e.g., the one or more cell, the second cell)or a base station (e.g., the second base station); a hardware load(e.g., CPU, memory, storage, buffer, backhaul link, antenna, etc.); aradio resource occupancy ratio (e.g., resource utilization ofuplink/downlink resources and/or sidelink resources for the mode 1operation); and/or a hardware/software/resource load of the second basestation is equal to or larger than a threshold value. In an example, thesecond base station may determine to configure/switch/change the atleast one sidelink bearer to use radio resources based on the mode 2operation if network capacity (e.g., capacity of a base station, a cell,a resource pool, etc.) of the second base station is equal to or smallerthan a value.

In an example, the second base station may determine toconfigure/switch/change the at least one sidelink bearer to use radioresources based on the mode 2 operation based on at least one of: a CBRof the resource pool for the mode 2 operation is equal to or smallerthan a value; a CR of the first wireless device (e.g., channel occupancyratio of traffic of the first wireless device) for the resource poolconfigured for the mode 2 operation is equal to or smaller than a value;a CR of the first sidelink bearer (e.g., the one or more sidelinkbearers, the second sidelink bearer, etc.) (e.g., channel occupancyratio of traffic of the sidelink bearer) for the resource poolconfigured for the mode 2 operation is equal to or smaller than a value;an RSSI of sidelink radio resources (e.g., radio resources indicated inthe information request for the sidelink resource; the resource pool forthe mode 2 operation) is equal to or smaller than a value; and/or thelike. In an example, the resource pool for the mode 2 operation may be aresource pool of the one or more cells (e.g., a cell of the second basestation; the second cell; etc.) of the second base station.

In an example, the handover request acknowledge and/or the secondarynode configuration request acknowledge that the first base stationreceives from the second base station may comprise parameters indicatingthat the at least one sidelink bearer is configured/switched/changed touse radio resources based on the mode 2 operation. The RRC configurationmessage (e.g., the handover command message and/or the RRCreconfiguration message) may comprise parameters indicating that the atleast one sidelink bearer is configured/switched/changed to use radioresources based on the mode 2 operation.

In an example, as shown FIG. 28, FIG. 29, FIG. 35, and/or FIG. 36, afirst wireless device may establish a first sidelink bearer between thefirst wireless device and a second wireless device. The first sidelinkbearer may be configured to use radio resources based on a mode 2operation. The first wireless device may send, to a first base station,first bearer configuration parameters of the first sidelink bearer. Thefirst wireless device may receive, from the first base station, a radioresource control configuration message comprising second bearerconfiguration parameters indicating that the first sidelink bearer isconfigured to use radio resources based on a mode 1 operation. The firstwireless device may send transport blocks of the first sidelink bearervia radio resources that are assigned based on the mode 1 operation.

In an example, the first wireless device may receive, from the firstbase station, an information request for a sidelink bearer that isconfigured to use radio resources based on the mode 2 operation. Thesending the first bearer configuration parameters may be based on theinformation request. The information request may indicate at least onereport condition to determine whether to send bearer configurationparameters of the sidelink bearer that is configured to use radioresources based on the mode 2 operation. The at least one reportcondition may comprise at least one of: a quality-of-service (QoS)requirement; a channel busy ratio (CBR) of a resource pool for the mode2 operation; a channel occupancy ratio (CR) of the first wireless devicefor a resource pool configured for the mode 2 operation; a channeloccupancy ratio (CR) of the sidelink bearer for a resource poolconfigured for the mode 2 operation; a received signal strengthindicator (RSSI) of sidelink radio resources; and/or the like.

In an example, the first wireless device may send, based on the firstbearer configuration parameters, transport blocks of the first sidelinkbearer via radio resources that are selected based on the mode 2operation. In an example, the establishing the first sidelink bearer maybe based on at least one system information block of a cell of the firstbase station. The establishing the first sidelink bearer may comprise:sending, by the first wireless device to the second wireless device, aconfiguration request for establishment of the first sidelink bearer;receiving, from the second wireless device, a configuration acknowledgeindicating completion of the establishment of the first sidelink bearer;and/or the like. The sending the configuration request may comprisesending the configuration request via at least one of: a PC5 radioresource control message; a PC5-RRC configuration/reconfigurationrequest message; a PC5-RRC UE information message; a directcommunication request message; and/or the like. The establishing thefirst sidelink bearer may comprise: sending, by the first wirelessdevice to the first base station, an information message requestingestablishment of the first sidelink bearer; receiving, from the firstbase station, a configuration message indicating that the first sidelinkbearer is configured to use radio resources based on the mode 2operation; and/or the like. The establishing the first sidelink bearermay be performed when the first wireless device is at least one of: in aradio resource control (RRC) idle state; in an RRC inactive state; whenserved by a base station other than the first base station; and/or thelike.

In an example, the first wireless device may send, to the secondwireless device and based on the second bearer configuration parameters,a configuration modification request for modification of the firstsidelink bearer. The first wireless device may receive, from the secondwireless device, a configuration modification acknowledge indicatingcompletion of the modification of the first sidelink bearer.

In an example, the mode 1 operation (e.g., dynamic grant, etc.) maycomprise at least one of: sending, by the first wireless device to thefirst base station, a grant request for the first sidelink bearer (e.g.,the grant request may comprise at least one of a buffer status report ora scheduling request); receiving, from the first base station and basedon the grant request, a sidelink grant indicating a radio resource;and/or the like. In an example, the mode 1 operation (e.g., configuredgrant, semi-persistent scheduling, etc.) may comprise at least one of:receiving, by the first wireless device from the first base station,resource configuration parameters indicating configured grant resources(e.g., a type 1 configured grant resources, a type 2 configured grantresources, and/or semi-persistent scheduling resources, etc.); selectinga radio resource from the configured grant resources for packettransmission of the first sidelink bearer; and/or the like. In anexample, the mode 2 operation may comprise selecting a radio resourcefrom a mode 2 resource pool for packet transmission of the firstsidelink bearer.

In an example, the first bearer configuration parameters may indicatethat the first sidelink bearer is configured to use radio resourcesbased on the mode 2 operation. The first bearer configuration parametersmay indicate at least one of: a bearer identifier of the first sidelinkbearer; a quality-of-service (QoS) requirement of the first sidelinkbearer (e.g., the QoS requirement comprising at least one of: 5QI, ARP,Priority level, Latency, Loss rate, etc.); a channel occupancy ratio(CR) of the first sidelink bearer (e.g., for a resource pool configuredfor the mode 2 operation); a field (e.g., cast type) indicating whetherthe first sidelink bearer is for a unicast transmission, a multicasttransmission (e.g., group cast), and/or a broadcast transmission; aservice type; network slice information; a cast type; performancemeasurement results of the first sidelink bearer (e.g., the performancemeasurement results indicating at least one of: whether the QoSrequirement is met based on a mode 2 operation; measuredquality-of-service information; etc.); a destination identifier of thefirst sidelink bearer (e.g., the destination identifier indicating atleast one of: a service associated with the first sidelink bearer, thesecond wireless device, and/or the like); PPPR/PPPP; a resource poolthat is used for the first sidelink bearer; at least one QoS flow mappedto the first sidelink bearer;

In an example, the first bearer configuration parameters may comprise atleast one of: a bearer identifier (e.g., SLRB Identity) of a sidelinkbearer (e.g., for unicast/groupcast/broadcast) for at least one oftransmission and/or reception; a destination identifier of a sidelinkbearer (e.g., for unicast/groupcast/broadcast) for at least one oftransmission and/or reception; a cast type of a sidelink bearer (e.g.,for unicast/groupcast/broadcast) for at least one of transmission and/orreception; a list of at least one QoS flow mapped to a sidelink bearer(e.g., for unicast/groupcast/broadcast) for at least one of transmissionand/or reception; a transmission range of a sidelink bearer (e.g., basedon distance to a destination wireless device); a discard timer (e.g.,for packet discard) of a sidelink bearer (e.g., forunicast/groupcast/broadcast) for at least one of transmission and/orreception; a PDCP sequence number (SN) size of a wireless device and/ora sidelink bearer (e.g., for unicast/groupcast/broadcast) for at leastone of transmission and/or reception; a maximum context identifier(e.g., maxCID) of a wireless device and/or a sidelink bearer (e.g., forunicast/groupcast/broadcast) for at least one of transmission and/orreception; a robust header compression (ROHC) profile of a wirelessdevice and/or sidelink bearer; a T-reordering timer of a sidelink bearer(e.g., for unicast/groupcast/broadcast) for at least one of transmissionand/or reception; an OutOfOrderDelivery indication of a sidelink bearer(e.g., for unicast/groupcast/broadcast) for at least one of transmissionand/or reception; an RLC mode of a sidelink bearer (e.g., forunicast/groupcast/broadcast) for at least one of transmission and/orreception; an RLC SN field length of a sidelink bearer (e.g., forunicast/groupcast/broadcast) for at least one of transmission and/orreception; a T-Reassembly timer (e.g., timer for reassembly) of asidelink bearer (e.g., for unicast/groupcast/broadcast) for at least oneof transmission and/or reception; a T-PollRetransmit timer of a sidelinkbearer (e.g., for unicast/groupcast/broadcast) for at least one oftransmission and/or reception; a PollPDU of a sidelink bearer (e.g., forunicast/groupcast/broadcast) for at least one of transmission and/orreception (e.g., for RLC AM, value p4 may correspond to 4 PDUs, value p8may correspond to 8 PDUs and/or the like, infinity may correspond to aninfinite number of PDUs); a PollByte is of a sidelink bearer (e.g., forunicast/groupcast/broadcast) for at least one of transmission and/orreception (e.g., for RLC AM, value kB25 may correspond to 25 kBytes,value kB50 may correspond to 50 kBytes and/or the like, infinity maycorrespond to an infinite amount of kBytes); a MaxRetxThreshold (e.g.,maximum number of retransmission) of a sidelink bearer (e.g., forunicast/groupcast/broadcast) for at least one of transmission and/orreception; a T-StatusProhibit timer (e.g., timer for status reporting)of a sidelink bearer (e.g., for unicast/groupcast/broadcast) for atleast one of transmission and/or reception; a LogicalChannelIdentity ofa sidelink bearer (e.g., for unicast/groupcast/broadcast) for at leastone of transmission and/or reception; a LogicalChannelGroup of asidelink bearer (e.g., for unicast/groupcast/broadcast) for at least oneof transmission and/or reception; a Priority of a sidelink bearer (e.g.,for unicast/groupcast/broadcast) for at least one of transmission and/orreception; a PrioritizedBitRate of a sidelink bearer (e.g., forunicast/groupcast/broadcast) for at least one of transmission and/orreception; a BucketSizeDuration (e.g., logical channel bucket sizeduration) of a sidelink bearer (e.g., for unicast/groupcast/broadcast)for at least one of transmission and/or reception; aConfiguredGrantTypelAllowed indication indicating whether a sidelinkbearer (e.g., for unicast/groupcast/broadcast) for at least one oftransmission and/or reception is allowed or not; a SchedulingRequestIDfor a sidelink bearer (e.g., for unicast/groupcast/broadcast) for atleast one of transmission and/or reception; aLogicalChannelSR-DelayTimerApplied of a sidelink bearer (e.g., forunicast/groupcast/broadcast) for at least one of transmission and/orreception; HARQ related information of a sidelink bearer (e.g., forunicast/groupcast/broadcast) for at least one of transmission and/orreception; and/or the like.

In an example, the second bearer configuration parameters may indicateat least one of: configured grant resources; a mode 1 resource pool; acell identifier of a cell associated with the mode 1 resource pool;and/or the like. The second bearer configuration parameters may compriseat least one updated parameter of the first bearer configurationparameters. The first base station and/or the second base station mayupdate/reconfigure one or more elements of the first bearerconfiguration parameters to the at least one updated parameter that thesecond bearer configuration parameters comprise.

In an example, the radio resource control configuration message may beat least one of: an RRC reconfiguration message; an RRC resume message;an RRC setup message; an RRC reestablishment message; a handover commandmessage; and/or the like.

In an example, as shown in FIG. 31 and/or FIG. 37, a second base stationmay receive, from the first base station, a handover (e.g., s-nodeconfiguration) request message comprising the first bearer configurationparameters of the wireless device. The second base station maydetermine, based on the first bearer configuration parameters, thesecond bearer configuration parameters for the wireless device. Thesecond base station may send, to the first base station, a handover(e.g., s-node configuration) request acknowledge message comprising thesecond bearer configuration parameters. The radio resource controlconfiguration message may be a handover command message based on thehandover request acknowledge message.

In an example, the first wireless device may establish a PC5 radioresource control connection with the second wireless device. The firstsidelink bearer may be associated with the PC5 radio resource controlconnection. The first sidelink bearer may be for multicast/broadcast toat least one wireless device comprising the second wireless device. Inan example, the first base station may determine, based on the firstbearer configuration parameters and resource status of a cell, toconfigure the first sidelink bearer to use radio resources based on themode 1 operation. The resource status of the cell may comprise at leastone of: a resource utilization of a mode 1 resource pool of the cell; aresource utilization of Uu resources of the cell; a CBR/CR/RSSI of amode 1 resource pool of the cell; and/or the like.

In an example, as shown in FIG. 30, the first base station maydetermine, based on resource status of a cell, to configure the firstsidelink bearer to use radio resources based on the mode 2 operation.The first base station may send, to the first wireless device, a secondradio resource control configuration message comprising third bearerconfiguration parameters indicating that the first sidelink bearer isconfigured to use radio resources based on the mode 2 operation.

In an example, the first wireless device may establish a second sidelinkbearer between the first wireless device and the second wireless device.The second sidelink bearer may be configured to use radio resourcesbased on the mode 2 operation. The first wireless device may send, tothe first base station, bearer configuration parameters of the secondsidelink bearer. The first wireless device may receive, from the firstbase station, a configuration message comprising bearer configurationparameters indicating that the second sidelink bearer is configured touse radio resources based on the mode 2 operation. The first wirelessdevice may send transport blocks of the second sidelink bearer via radioresources selected based on the mode 2 operation.

In an example, a first base station may receive, from a first wirelessdevice, first bearer configuration parameters of a first sidelink bearerbetween the first wireless device and a second wireless device. Thefirst sidelink bearer may be configured to use radio resources based ona mode 2 operation. The first base station may determine, based on thefirst bearer configuration parameters and resource status of a cell, toconfigure the first sidelink bearer to use radio resources based on amode 1 operation. The first base station may send, to the first wirelessdevice, a radio resource control configuration message comprising secondbearer configuration parameters indicating that the first sidelinkbearer is configured to use radio resources based on the mode 1operation. The first base station may assign radio resources for thefirst sidelink bearer of the first wireless device (e.g., based on themode 1 operation).

In an example, a first base station may receive, from a first wirelessdevice, first bearer configuration parameters of a first sidelink bearerbetween the first wireless device and a second wireless device. Thefirst sidelink bearer may be configured to use radio resources based ona mode 2 operation. The first base station may receive a measurementresult of a cell of a second base station. The first base station maysend, to the second base station and based on the measurement result, ahandover (e.g., s-node configuration) request message comprising thefirst bearer configuration parameters of the wireless device. The firstbase station may receive, from the second base station, a handover(e.g., s-node configuration) request acknowledge message comprisingsecond bearer configuration parameters determined based on the firstbearer configuration parameters. The second bearer configurationparameters may indicate that the first sidelink bearer is configured touse radio resources based on a mode 1 operation. The first base stationmay send, to the first wireless device, a handover command messagecomprising the second bearer configuration parameters.

In an example, the second base station may determine, based on the firstbearer configuration parameters and resource status of the cell of thesecond base station, to configure the first sidelink bearer to use radioresources based on the mode 1 operation. The second base station mayassign, radio resources for the first sidelink bearer of the firstwireless device based on the second bearer configuration parameters.

In an example, a first wireless device may establish a first sidelinkbearer between the first wireless device and a second wireless device.The first sidelink bearer may be configured to use radio resources basedon a mode 2 operation. The first wireless device may send, to a firstbase station, first bearer configuration parameters of the firstsidelink bearer. The first wireless device may receive, from a secondbase station (e.g., via the first base station), a radio resourcecontrol configuration message (e.g., a handover command message, an RRCreconfiguration message, etc.) comprising second bearer configurationparameters. The second bearer configuration parameters may indicate thatthe first sidelink bearer is configured to use radio resources based ona mode 1 operation. The first wireless device may send transport blocksof the first sidelink bearer via radio resources that are assigned basedon the mode 1 operation.

In an example, the first wireless device may send, to the first basestation, a measurement result of a cell of the second base station. Thefirst wireless device may receive, from the first base station, ahandover command message indicating a handover to the cell of the secondbase station (e.g., the handover command message is the radio resourcecontrol configuration message from a second base station). The firstwireless device may perform a random access to the cell of the secondbase station for an RRC connection with (e.g., handover to) the secondbase station. The radio resource control configuration message may beassociated with the RRC connection with the second base station.

In an example, a first wireless device may send, to a first basestation, a configuration request for a sidelink bearer. The firstwireless device may receive, from the first base station, bearerconfiguration parameters for the sidelink bearer. The bearerconfiguration parameters may indicate that the sidelink bearer isconfigured to use radio resources based on a mode 1 operation. The firstwireless device may receive, from the first base station, a radioresource control configuration message indicating that the sidelinkbearer is configured to use radio resources based on a mode 2 operation.The first wireless device may send transport blocks of the sidelinkbearer via radio resources selected based on the mode 2 operation.

FIG. 38 is a flow diagram of an aspect of an embodiment of the presentdisclosure. At 3810, a first wireless device receives from a basestation, an indication of a sidelink bearer to transition from aresource allocation mode 1 to a resource allocation mode 2. At 3820, thefirst wireless device transmits transport blocks via the sidelink bearerto a second wireless device based on the indication.

1. A method comprising: receiving, by a first wireless device from abase station, configuration parameters for a resource allocation mode 1of a sidelink bearer between the first wireless device and a secondwireless device; receiving, by the first wireless device from the basestation, at least one parameter indicating the sidelink bearer totransition from the resource allocation mode 1 to a resource allocationmode 2; and transmitting, by the first wireless device to the secondwireless device, transport blocks via the sidelink bearer based on theresource allocation mode
 2. 2. The method of claim 1, wherein theconfiguration parameters are for a plurality of sidelink bearers betweenthe first wireless device and the second wireless device, the pluralityof sidelink bearers comprising the sidelink bearer.
 3. The method ofclaim 2, further comprising transmitting, by the first wireless deviceto the second wireless device, second transport blocks via at least oneother sidelink bearer of the plurality of sidelink bearers based on theresource allocation mode 1 after receiving the at least one parameterindicating the sidelink bearer to transition.
 4. The method of claim 3,further comprising configuring, by the first wireless device, theplurality of sidelink bearers based on the configuration parameters. 5.The method of claim 4, wherein the configuring the plurality of sidelinkbearers comprises: sending, by the first wireless device to the secondwireless device and based on the configuration parameters, aconfiguration request for the plurality of sidelink bearers; andreceiving, by the first wireless device from the second wireless device,a configuration request acknowledge indicating a configurationcompletion of the plurality of sidelink bearers.
 6. The method of claim1, wherein the transmitting the transport blocks comprises transmittingthe transport blocks associated with the sidelink bearer via radioresources that are determined based on the resource allocation mode 2.7. The method of claim 1, further comprising transmitting, by the firstwireless device to the second wireless device, third transport blocksvia the sidelink bearer based on the resource allocation mode 2 beforereceiving the at least one parameter indicating the sidelink bearer totransition.
 8. The method of claim 2, further comprising transmitting,by the first wireless device to the base station, an information messagecomprising information of the plurality of sidelink bearers comprisingthe sidelink bearer, wherein the configuration parameters are based onthe information message.
 9. The method of claim 8, wherein theinformation message comprises at least one of: bearer identifiers of theplurality of sidelink bearers; quality-of-service (QoS) requirements ofthe plurality of sidelink bearers; an indication indicating whether eachof the plurality of sidelink bearers is for a unicast or a multicast; aQoS measurement result of the plurality of sidelink bearers, the QoSmeasurement result comprise at least one of: a parameter indicatingwhether a QoS requirement of one or more of the plurality of sidelinkbearers is met; a measured packet loss rate; a measured latency; or ameasured throughput. a destination identifier of the plurality ofsidelink bearers, the destination identifier indicating at least one of:a service associated with the plurality of sidelink bearers; or thesecond wireless device; a resource pool that is used for the pluralityof sidelink bearers; or at least one QoS flow mapped to the plurality ofsidelink bearers.
 10. The method of claim 8, further comprisingreceiving, by the first wireless device from the base station, aninformation request for the plurality of sidelink bearers, wherein thetransmitting the information message is based on the informationrequest.
 11. A first wireless device comprising: one or more processors;and memory storing instructions that, when executed by the one or moreprocessors, cause the first wireless device to: receive, from a basestation, configuration parameters for a resource allocation mode 1 of asidelink bearer between the first wireless device and a second wirelessdevice; receive, from the base station, at least one parameterindicating the sidelink bearer to transition from the resourceallocation mode 1 to a resource allocation mode 2; and transmit, to thesecond wireless device, transport blocks via the sidelink bearer basedon the resource allocation mode
 2. 12. The first wireless device ofclaim 11, wherein the configuration parameters are for a plurality ofsidelink bearers between the first wireless device and the secondwireless device, the plurality of sidelink bearers comprising thesidelink bearer.
 13. The first wireless device of claim 12, wherein theinstructions further cause the first wireless device to transmit, to thesecond wireless device, second transport blocks via at least one othersidelink bearer of the plurality of sidelink bearers based on theresource allocation mode 1 after receiving the at least one parameterindicating the sidelink bearer to transition.
 14. The first wirelessdevice of claim 13, wherein the instructions further cause the firstwireless device to configure the plurality of sidelink bearers based onthe configuration parameters.
 15. The first wireless device of claim 14,wherein the configuring the plurality of sidelink bearers comprises:sending, by the first wireless device to the second wireless device andbased on the configuration parameters, a configuration request for theplurality of sidelink bearers; and receiving, by the first wirelessdevice from the second wireless device, a configuration requestacknowledge indicating a configuration completion of the plurality ofsidelink bearers.
 16. The first wireless device of claim 11, wherein thetransmitting the transport blocks comprises transmitting the transportblocks associated with the sidelink bearer via radio resources that aredetermined based on the resource allocation mode
 2. 17. The firstwireless device of claim 11, wherein the instructions further cause thefirst wireless device to transmit, to the second wireless device, thirdtransport blocks via the sidelink bearer based on the resourceallocation mode 2 before receiving the at least one parameter indicatingthe sidelink bearer to transition.
 18. The first wireless device ofclaim 12, wherein the instructions further cause the first wirelessdevice to transmit, to the base station, an information messagecomprising information of the plurality of sidelink bearers comprisingthe sidelink bearer, wherein the configuration parameters are based onthe information message.
 19. The first wireless device of claim 18,wherein the information message comprises at least one of: beareridentifiers of the plurality of sidelink bearers; quality-of-service(QoS) requirements of the plurality of sidelink bearers; an indicationindicating whether each of the plurality of sidelink bearers is for aunicast or a multicast; a QoS measurement result of the plurality ofsidelink bearers, the QoS measurement result comprise at least one of: aparameter indicating whether a QoS requirement of one or more of theplurality of sidelink bearers is met; a measured packet loss rate; ameasured latency; or a measured throughput. a destination identifier ofthe plurality of sidelink bearers, the destination identifier indicatingat least one of: a service associated with the plurality of sidelinkbearers; or the second wireless device; a resource pool that is used forthe plurality of sidelink bearers; or at least one QoS flow mapped tothe plurality of sidelink bearers.
 20. A system comprising: a firstwireless device comprising: one or more processors; and memory storinginstructions that, when executed by the one or more processors, causethe first wireless device to: receive, from a base station,configuration parameters for a resource allocation mode 1 of a sidelinkbearer between the first wireless device and a second wireless device;receive, from the base station, at least one parameter indicating thesidelink bearer to transition from the resource allocation mode 1 to aresource allocation mode 2; and transmit, to the second wireless device,transport blocks via the sidelink bearer based on the resourceallocation mode 2; and a base station, wherein the base stationcomprises: one or more processors; and memory storing instructions that,when executed by the one or more processors, cause the base station to:transmit, to the first wireless device, the configuration parameters forthe resource allocation mode 1 of the sidelink bearer between the firstwireless device and the second wireless device; and transmit, to thefirst wireless device, the at least one parameter indicating thesidelink bearer to transition from the resource allocation mode 1 to theresource allocation mode 2.